Ignacio,
I'm going to post this in case anyone else has a related bug in their code.
Before using TDbfDataSet:Update() to save changes, I was issuing a
TDbfDataSet:SaveState(.T.) and then seeking the value of a primary key to
insure that no duplicates were added to the table. Then I was issuing a
TDbfDataSet:RestoreState(.T.) I misunderstood the documentation example for
SaveState() and therefore the parameter .T. was UN-linking the datacontrol.
Changing the lines to SaveState() and RestoreState() fixed the problem for
me.
Gary
"Ignacio Ortiz de Zúñiga" <
NoNameToAvoidSpam@xailer.com> wrote in message
news:49fea197$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Gary,
>
> That control is used by example on datacontrolsDbfData1.
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> Xailer support / Soporte de Xailer
>
http://www.xailer.com
>
http://www.xailer.info
> "Gary S. Rogers" <
g.s.rogers@att.net> escribió en el mensaje
> news:[email=49fe53d9@svctag-j7w3v3j....]49fe53d9@svctag-j7w3v3j....[/email]
>> I'm not getting this control to work. When linked to a dataset and
>> datafield, the control doesn't seem to accurately reflect the state of
>> the underlying data field, nor does checking or unchecking the box change
>> the underlying data field on update().
>>
>> Anyone else having problems with this control in 2.0?
>>
>> TIA,
>> Gary
>>
>
>