Thanks for the infornation. I assume the 5/7/99 Vfp6r.dll in the windows\system is the correct dll for VFP SP3. But how could i verify that? Because now I have found one of my client sites with a 5/15/99 Vfp6r.dll.

Brenda


>Doing a copy just isn't a good idea. There are files that need to be in specific directories and still others that need to be registered. Look at chapters 25 & 26 of the VFP Programmer's Guide for information on how to create distribution disks. As for service packs, one solution is to create a setup that just includes the new runtime DLLs. Remeber that with Fox, your EXE is just token-ized code. It then gets read by the runtime DLLs and executed, so yes, if you run code with older SP runtimes, it can cause problems.


>>My application does not do an install. All the required DLLs are in the folder with the myprog.exe file. When I do a new release I just copy over the new myprog.exe. When we switched from VFP5 to VFP6 I also copied over the new DLL. But what about service packs? I did a find on my PC for "Vfp6r.dll" and found one dated 5/7/99, in my windows\system and another in myapplication folder dated 6/16/98. Was the 5/7/99 Vfp6r.dll because of a SP?
>>
>>Do some service packs have new DLLs? I am confused about if I build my exe using VFP SP3 but execute it with an older DLL can that cause problems?
>>