I've run into this on 2 systems, both NT Server (although that may have nothing to do with it). On one we only needed a single file and we opened and closed it as needed. The other was more complicated, using views, so we ended up doing a requery() IF a file on the server had been updated. Part of our SAVE routine on the 3 tables involved was to update the file.

This SHOULD be handled by the refresh, but I couldn't get it to work.

Barbara

>Barbara,
>
>I've made sure the default datasession has now tables open.
>I've got the Refresh down to 1,1
>I've refreshed the forms in the activiate event.
>
>I do not reopen the tables. I open them in the dataenvironment, set to optimistic row buffering. The same table is open in the parent form and is also set to optimistic row buffering. When I view the same form on two different pc's, the same data show different on both. It looks ok on the 1st pc that changed it, but on the 2nd pc it still looks like the original.
>
>I do not understand. This is straight open the table in the dataenvironment, private datasession, update it, unlock it and release the form. I cannot see why the other user see's the original values.
>
>I really was hoping I did not have to managing opening and closing the table outside the dataenvironment.
>
>Anything else I can do before I go to that extreme?
>
>I appreciate your help and info.
>
>John
>
>