>>>>I am preparing to upgrade from VFP 3.0 (not 3.0b) to VFP 5.0 (not 5.0a). As I understand from other threads, I need to uninstall VFP 3.0 from my c-drive and install 5.0 as if Visual FoxPro were a totally new creature to live on my PC. Is this correct?
>>>>
>>>>After upgrading the programming environment, I need to upgrade my project to VFP 5.0. To do this, I simply bring up the project in 5.0 and recompile ALL files - correct?
>>>>
>>>>TIA for any assistance.
>>>
>>>Generally, it is not necessary to remove VFP 3.0. You just have to install VFP 5.0 to different directory.
>>>If you try to open VFP 3.0 project in 5.0, it will suggest you to convert it.
>>>There are several options involved. Don't forget to have backup copy of VFP 3.0 project.
>>>
>>>Nick
>>
>>
>>Okay, so going from 3.0 to 5.0 at my desk is much easier than I thought. That's quite a releif.
>>
>>What about the delivered application. I installed the 3.0 application on my customer's server from setup disks created by VFP 3.0's install (deliver?) process. I have updated the application by creating a new executable and providing it to the customer. At the same time I provide fresh copies of the application's .DBC, .DCT, and .DCX ; all four files provided via a self extracting archive.
>>
>>When I deliver the new 5.0 application, I assume I need to create new setup disks for the customer, true?
>>
>>My customer allowed access to the application from other workstations by copying file VFP300.ESL to each workstation's window directory. This may not have been the normal way to do it, but it works. The executable and database tables remain on the server. When I deliver the new 5.0 applications, how do I handle this?
>>
>>Sorry to seem so naive about these sort of things, but I've never had to support a networked windows app before.
>>
>Normal way of installing VFP application includes:
>1. Using setup wizard to generate installation package (Netsetup preferred). This package shouldn't include database related files
>2. Reside Netsetup on server.
>3. Each user runs Setup.exe (from Netsetup package) installing executable locally (it might be icon on user's machine to repeat installation later on).
>
>Old way (Fox 2.x) of copying just ESL file works incidentally, but can yield unexpected results in run-time.

I agree with Edward, and VFP500.DLL has to be included into setup to reside in WINDOWS/SYSTEM, just copying in this case doesn't work anymore.