I think I understand why you say Hmmmm. It is indeed a decision about a fundamental principle in the technical design. And it may require some study time because there are some related functions and concepts too that need to be studied and practiced.
>Oh, I understand that I can turn oun buffering, all right. I've actually been working in another thread on that very concept.
>
>Of course, since it's not implemented now, I'd have to do some different work to make sure that the records get posted later ... right now, unbuffered, the changes are posted immediately.
>
>Hmmmmmm
>
>>But you can use CURSORSETPROP() just for that. See the example in the doc.
>>
>>>No, I hadn't -- because I had never heard of it.
>>>
>>>However, for the case in hand, the table isn't being buffered, so I don't think it applies.
>>>
>>>>>I have a few fields on a stand alone table where I want to save a log of all changes.
>>>>>
>>>>>Do I write to the log file in the VALID method? And do I know that I need to do so by saving a flag that INTERACTIVECHANGE was called (in case they just tabbed through)?
>>>>
>>>>Did you already read the help on GETFLDSTATE() ?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
