>>Hi All:
>>
>>Okay, so its already been established that we have to upgrade our client runtime files so we can take advantage of SP3. Our site can deliver updated files to the client workstations (using netware utility programs), if I can set up the changes on a test PC for the network guys to take 'snapshots' before and after. Question: Rather than recompile our root EXE loader (which runs the other FXPs, SCXs, etc.) and make a new set of setup disks for this, could I just use the existing setup disks on the PC then apply SP3 to *that*? Would it be smart enough to know that only the runtime files are there and take care of them? Reason for this is that I'm on a tight deadline, and if I can avoid the new setup disks part it will save a little badly needed time for me. But I don't want to put reliability in jeopardy... Please advise.
>>
>>TIA
>>
>>Rob
>
>OK I'm going to admit up front that this is a hack, but I've upgraded about 20 users to SP3 this way and they seem to be getting along fine.
>
>Upgrade a runtime workstation to service pack 3.
>
>Copy the following files from that machine's \Windows\system directory to the network:
>
>VFP6Run.Exe
>VFP6r.dll
>vfp6renu.dll
>
>Go to a workstation you want to upgrade and copy those files from the network back down to \windows\system.
>

And massively suicidal, since some of the things that changed with SP3 are not just the VFP runtime components; there are also updated shared components in the various service packs that may need to be put in place, and at a minimum, the two runtime .DLLs need to be registered to ensure that the correct details are present in HKEY_CLASSES_ROOT.

>Like I said, I know this is a bit of a cheat, but it has worked for me.