>>We have huge problems with requery if we run the stuff over the net. It works fine as long as only one user is on it. As soon as a second process opens a table, the table will be reloaded over the net on every requery we do. If only one user is active, the data will not be rearead. This happens if the data is changed or not and will stop only of all user close the table. Led up to endless reload times.
>
>This is by default. I think there might be some tweaking possible. What you are describing is the oplocking mechanism. If only one user has opened a file, that users machine will cache read and write buffers locally. If another user on the network has opened the file, the PC of the first user is asked to flush its write buffers. If they are clean, two users can still cache read buffers, bat as soon as one writes to the table, all client caching will be disabled.

Exactly. I forgott the name on it. It simply makes VFP over the network unusable on tables that are a little bit larger. One can try to do the workaround with a local mirror database, but your customers figured out that a TerminalServer was easier. We still think about a web based solution, but the customer wants a flexibility like Excel on the one side and database on the other. So we have a problem here.

Agnes