Sorry, you probably already did this - how about placing the new vfp6r.dll in the same directory as SS.exe. I believe that in VFP 6, the app will look in the same directory first before going to the system directory. I know this is how the nulti-threaded version(vfp6t.dll) works.
>I think you could just do a regsvr32 on the new vfp6r.dll ...
>>I have a problem with some our clients running our vfp app. Inadvertently, they ended up with more than one copy of the vfp runtime files(vfp6r.dll and vfp6renu.dll).
>>
>>We try to fix this problem by:
>>
>>1 unregistering the ones we want to get rid of with regsvr32.
>>2 renaming these files to .old
>>3 copying/registering the runtimes where we want it to find them.
>>4 rebooting the machine
>>
>>When they fire up our application(SS.EXE), it bombs because it is still looking for the runtimes where they used to be.
>>
>>Any ideas?