>Imagine you have updatable local view with optimistic buffering (5). When you want to save changes to involved table, all you would to do is to issue TABLEUPDATE(.T.) on the view. But...
>The table musn't be buffered. If not, you have to issue second TABLEUPDATE on the updated table.
>
>The question:
>How to force the table to be not buffered in DE?
>
>Answer 1 (wrong):
> Set the form's BufferMode to '0-None'
> Set DE.table's BufferModeOverride to '1-Use Form Setting'
>
>Answer 2 (working):
> Ignore form's buffering setting - set '0-None' directly to DE.table.
>
>Do you know any other solutions?
Are you including the table in the DE? I just built a view, added it to a form, set buffering to 5, dropped it on the form as a grid, added a button with
IF !TABLEUPDATE(2)
MESSAGEBOX("Problem!")
ENDIF
and ran the form. I changed a number of records, clicked the button and the update worked. I verified the changes in the original table and the changes were there.
So it's not necessary to add the table the view is based on to the DE.
HTH,
Jim Duffy
Microsoft MVP
INETA Speaker
TakeNote TechnologiesDeveloper's Choice Award Winner for Best Training Company
Specializing in VB.NET, ASP.NET, VFP, and SQL Server Training and Development