Steve,

One way, is before running the scan, you show it on the screen behind the form:

activate screen
CURSORGETPROP('buffering', 'dieactualdata')

You can change buffering using cursorsetprop() function. Maybe it didn't work outside the scan because you didn't tell it what table to tableupdate(), and the other table would have been selected at that point.

Having the tableupdate() inside the SCAN is fine.

Instead of using dataenvironment of form, you can open tables in the load() of the form. I prefer this method.

>OK, the tableupdate after the gather fixed the problem. I tried it after the endscan, but that didnt work.
>
>Where do I go to see if i am using row or table buffering?
>
>When I look at the properties of my cursor, I see the options for row & table, but mine is set to form default. SO I go to the form and the buffermode is set to 2 optimistic. There is nothing listed about row or table.


>OK, the tableupdate after the gather fixed the problem. I tried it after the endscan, but that didnt work.
>
>Where do I go to see if i am using row or table buffering?
>
>When I look at the properties of my cursor, I see the options for row & table, but mine is set to form default. SO I go to the form and the buffermode is set to 2 optimistic. There is nothing listed about row or table.