General information
Category:
Coding, syntax & commands
>>>>
>>>>Why don't you like to have Table buffering, updating table once when finishing all data entry and closing the view?
I tried the table buffering, but the app would freeze up after a couple of edits -- I am forcing a save when the user moves off the record. I think just too much was going on!
>>>
>>>If you need to be able to recover 1 row at a time, why not just circumvent TableRevert altogether and dump (SCATTER) each row to an array which is a property of the form. Then use a GATHER to revert instead of TableRevert. If this is a multi-user app, you'll need to issue an RLOCK() for each rowchange and then an UNLOCK prior to each rowchange
>>>
>>>HTH
>>
>>I used to do something similar, but as usual I prefer cursors, and Matt likes arrays :)
>
>The more things change, the more they stay the same. ;-)
Thanks guys, I'll give this a shot. Arrays, or cursors, makes no difference to me! :)
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only