>Hi,
>
>Recently, I've developed a complex single-user application for a client. However, after I completed the application, the client suddenly decided that he wanted the capability for two users to add and edit data simultaneously. The client does not own VFP, so I've created an "exe" and will be using the setup wizard to create an installation program. Basically, they will have two computers. "User 1" will be running the application directly from the computer on which the application resides, and "User 2" will be running the application from a computer networked into the computer of "User 1".
>
>Well, I could use some feedback as to whether I'm setting this up correctly. I've never configured a multi-user VFP application, so I'm not quite sure if I'm going about this correctly. This is what I've done so far:
>
>I've set the the "DataSession Property" of the forms to "private data session". I also set the "BufferMode Property" of the forms to "Pessimistic". I've developed custom messages which are triggered if both users try to edit the same record at the same time. I'm assuming that the DataSession and Buffermode property settings will allow basic multi-user functionality at the least. Is this a correct assumption??
>
>I realize that I could make this more robust, but the client needs this application ASAP, and there is only a very remote chance that the users will ever edit the same record at the same time. So, does this seem ok?
>
>My other question is about installing the application. Again, the client will not have the full-version of VFP on either of his computers. I will be making a self-standing version with the VFP setup wizard. I will install the self-standing application and all of it's files on one computer only, and the second computer will run the application from over the network. Is this correct?
>
>The reason I'm asking this is because I've worked with Microsoft Access, and with that product, either the retail or runtime version of Access had to be installed on both computers. Otherwise, there would supposedly be a problem with too much being pulled over the network at once. Basically, the form objects would reside on the workstations and the data would reside on a backend.
>
>Anyway, any advice or feedback on this would be much appreciated.
>

Barbara pretty much covered it all.
One way to install runtimes on the second machine is to download the VFP runtime setup app that is in the file section of UT. It uses an empty prg file and compiles it to an EXE, then uses the setup wizard to create an install exe.
Run it on the machine that doesn't have the VFP developer on it.

I would add that you may want to use OPTIMISTIC buffermode=5 (table mode) because of some esoteric bugs in mode 3 (row mode) and make buffermode 5 behave like buffermode 3 by your settings on TABLEUPDATE and TABLEREVERT. Unless, or course, you are deliberately updated multiple rows at one time. IF you are sure that the two operators won't be editing the same record at the same time you can use the "BRUCE WILIS" record locking approach - last record saved wins. Otherwise you will want to investigate the use of RLOCK and related functions. Make sure the tables in your dataenvironment are SHARED.