>No, nothing like that has happened. We do get errors when that does happen but this is not the case this last time. The errors we get are not occurring each time. It happens various times in different tables, databases, fields etc. For example, when we are cleaning a database, we might have a dirty name of Ryan Oneil. So we clean it to say Ryan O'Neil, to be correct. Then let's say we also include a salutation field to say Mr Ryan O'Neil. On one screen it will have everything correct. On another, when we check it again, it will be correct there as well. But if either of us close the database, then open it again, something might be wrong, changed or half finished. Example, it may say dirtyname Ryan Oneil, cleanname Ryan O'Neil but still have Mr Ryan Oneil for the salutation, even after we checked it. It doesn't happen all the time, nor does it happen on specific databases. Its as though Fox saves part of the table with one person working on it, and then while others are in, it attempts
>to save, gets confused, doesn't save the last save to disk, but instead saves a middle copy. Even though, while both of us are in it, we can see the changes, everything seems ok, so we close it. Then maybe the next day, it will be off again, or sometimes an hour or two later.
>I have some replies that I have gotten from various people. I can send those to you if you'd like. I'm really at a loss here. It's not happening enough to be a huge problem. But it happens enough to be annoying.
>
>Thank you in advance,
>
>Michael Todd
>Network Administrator
>Paragon Company
>mike.todd@paragonco.com

If your users are manually editing fields in the table, and other users are also manually in the tables at the same time... you could get strange results. Do you have someone that could write an interface for you that would lock the records, update them, etc?


Just a thought
Wayne