>I have an app that has a find form and a contact form. Double-clicking on the Find form opens a Contact.
>
>Here's the problem: UserA does a search and opens Fred Flinstone, changes data, closes it. UserB open Fred Flinstone and makes changes. No problems so far. UserA then opens Fred again. UserA does not see the changes UserB has made. What gives?
>
>Some things I've found: The Find form opens the Contact table. If, for UserA, I close the Contact table that Find has open, and then open Fred, it works - you see the changes. If UserA does a Search for Fred and then opens it, it works.
>
>It doesn't appear to be a Write Cache problem. I've turned off write-cache. I've also let the computer set there for an hour, UserA still doesn't get the updated Fred.
>
>I've tried a host of FLUSHing, explicitly closing tables, etc. without much luck. Anybody have an idea?

Try changing the form's dataenvironment to close tables on exit. Regardless, if the first form is shutdown before the second edit starts then the first user going into the form after user 2 finshes should see the changes. If that isn't happening then there must be something happening with the data buffering - or some custom opening of tables/views/selects are going on. What are the forms' settings for datasession and buffermode?


Other random thoughts... (I know, it's a Friday)

Are you using views? If you select out of a view to a cursor, for example, and refresh your cursor - it refreshes from the view - not the original database(s). So if both edits are based on a select out of a view you can run into some scenarios that go beyond the standard 'last person who saves wins' scenario.

Are you doing transaction processing? Anything in the middle of a transaction doesn't get written until the end transaction during the update. All changes are invisible to everyone else until then. Even if you have a programmed save it doesn't matter if you also have an open transaction construct.

I could see setting up some select statements to fill a listbox/combobox/grid etc. along with a child select to grab the data to be edited. All of this is easily non attached to the original data - unless you program a custom save routine to write the data back out. So they updated the cursor - means nothing to the database till you tell it. How simple and straightforward of an edit form is it?