>>>>hi all
>>>>what are the steps to install a foxpro database in windows server 2003 std edition for all staff to access.
>>>>also what is the network enviroment for the above too.
>>>>
>>>>Thank you
>>>
>>>Just put the database on place where everyone can access it. The database is just files.
>>>
>>>Anyway this normaly will create big fat network load. There are also problems with multiuser access. We normaly set up a terminal server on this.
>>>
>>
>>While indeed any file-server based database approach causes increased network traffic, compared to just sharing a few Office documents or so, it's still the traditional way to access a FoxPro back-end, and works just fine.
>>So your advice sounds a little misleading to me.
>>
>>
>>-Stefan
>
>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.