>Dave,
>You won't need to have VFP on each computer, just the runtime libraries which you can get with the Setup Wizard. The first computer will need to have the EXE and data files as well as the runtime files. The other computer just needs to have the runtime files. If you use the same install program, just delete the EXE & data from the SECOND computer. When you make the shortcut for the second computer, point it to the mapped drive on the first.
>
>
>The most important thing you need to do is make sure you have "SET EXCLUSIVE OFF". You can put it in your Config.FPW, but that will only affect the default Datasession. Since you're using Private Datasessions, you'll need to place the SET command in the LOAD() code of each form (or in the LOAD() code of your base form if you have one).
>
>Second you should use optimistic buffering so no record is locked longer than it takes to save data. Only use pessimistic buffering in cases where it is imperative that data be available to only one user. With pessimistic buffering, you lock each record when the record pointer hits it. Imagine the problems if both of your users are scrolling through the data looking for a record. You can use CurVal() and OldVal() after editing to see if the other user changed data, but you do say that this will be a rare event.
>
>Good luck and don't hesitate to ask more questions.
>
>Barbara
>
Barbara:

I use exactly the procedures that you explain to David Rubin, installing my application in a server with Windows2000, and the runtime libraries in the other 3 computers. The application is running sucessfully.
But the programmer of my customer says that it would be better if my program (.EXE) would be running always in the server, without the runtime libraries in the other PC's, only with the shortcut; then he could install more PC's without any 'setup' of the VFP runtime libraries.
May be this possible ?

Many thanks