>>>>What is the best way to Save a record in a View all the way back to the table and to avoid errors? These apps are small stand alone or networked apps with little traffic on the net so speed is not an issue.
>>>>
>>>
>>>
>>>Do you have a buffered copy of the table open in the same work area? Sounds like maybew you are running into double buffering...
>>
>>Yes, the table and the view is open in the same work area... The table for some selects and the view for the record editing/adding...
>>
>>double buffering?? I thought that was limited to Washington DC....
>
>No, it's the cause of your troubles. What's happening is that when you do TABLEUPDATE() on your view, it's just writing the changes to the buffered copy of your table that's open in the same work area, and those changes are not being applied to the table on disk. If you need to keep that table open, either turn off buffering for that table (CURSORSETPROP("Buffering", 1)), or be sure and do a TABLEUPDATE() on the table after every TABLEUPDATE you do on the view.

Hi Eric,

Thanks for the reply. I really don't need the tables open except for the SELECT that prints the report. Should I not have the tables in the DE? Should I USE the tables after the SELECT? or is setting the Buffering off the best way to go?

Thanks