Dave,
Glad to help. To answer your questions:

1 & 2: I can see that this will add to your problems, however, you have the right idea - simplify everything for them.

3: You can do some testing by loading the application 2 or 3 times on your computer and testing the various forms - go to the same record, etc. This isn't as good as a real network test, but it will find many of the basic problems with locking.

4: Jerry's suggestion of getting the UT runtime files is good. I made my set with a small text file and copy it to a CD for each new client, carefully labeling it "XYZ Application WorkStation Installation Files". Looks very impressive (to them) with their own name and everything < grin >.

5: Runtime/library files mostly go into the Windows/System folders. The installer knows where to put them, depending on the operating system. This way the user can run many VFP programs, some on their computer and others on the network using the same files.

6: Yes, the second computer will need an icon to start the EXE on the primary computer. Don't forget that computer 2 will need read/write/delete/etc. access to ALL of the folders used by your EXE - data, reports, etc. There may need to be some work marking drives for sharing and mapping computer 1's drives to computer 2.

Hope this is clear, if not just ask....

Barbara



>Hi Barbara,
>
>Thank you so much for the help! It's so hard to find good information about multi-user issues.
>
>Part of my problem is the following:
>
>1) My client is out of state, so he will need to install the files on both computers without my physical presence or help.
>
>2) My client is just about computer illiterate. I had to spend almost one hour helping him find and install a demo file that I uploaded to them.
>
>3) I can't test this in a multi-user environment, since I only have a single computer where I work from.
>
>I need to figure out the simplest and most automated way to get the application installed and working on their network. I assume that making an installation program without the "exe" and database files would just involve selecting "Visual FoxPro Runtime" in "step two" of the setup wizard. "Step 6" should not contain any files, since the installion would only be installing the setup wizard runtime files. Is this correct?
>
>If I was able to physically perform the installation myself, I would take your suggestion by using the same installation file and then deleting the "exe" and database files. However, it will be too difficult trying to explain this to my client.
>
>After installing the runtime files on the second computer, the client would need to make a desktop shortcut to the drive and Application "Exe" on the other computer (where the application resides). Is this correct?
>
>I've read that the "exe" needs to be in the same folder as the runtime files. Since there is no "exe" on the second computer, how does this work? Does it matter where the runtime files are located on the second computer? Will the applicaton "exe" on the main computer be able to locate the runtime files on the second computer? My question might be confusing, since I'm confused about this. I guess I wouldn't be as confused if I could actually try this out for real.
>
>Anyway, thanks again for your help. I'm sure I will have a few more questions.
>
>Dave...:)