Hi Jeff,

Where did you get an idea that the rest of DLL's (besides VFP8R.DLL and VFP8T.DLL) have to be registered? See http://fox.wikis.com/wc.dll?Wiki~VFP8RuntimeFiles~VFP for detailed info about VFP8 runtime files.

>I have an application that is currently running in VFP6 that the client has finally agreed to cut over to a version compiled in VFP8.
>
>I plan to use the existing VFP6 application to install the VFP8 runtime DLLs and automatically start running the VFP8 version of the application if a success flag is set. This will allow the migration to occur without visiting each PC individually.
>
>I already have a module that performs the DLL registration and the users have full registry rights.
>
>Next I looked for message threads to see what VFP8 DLLs will probably be needed, and found the following candidates:
>
>vfp8r.dll
>vfp8t.dll
>gdiplus.dll
>msvcr70.dll
>vfp8renu.dll
>
>Then, I found that the registration for vfp8r.dll and vfp8t.dll went as planned, however, I get an invalid entry point error on the rest of the DLLs.
>
>I searched on the PCs for multiple versions of the various DLLs and also tried unsuccessfully to manually register them with DOS commands like:
>
>c:\windows\system32\regsvr32.exe gdiplus.dll
>
>I noticed that my VFP8 application seems to run OK with just the registration of vfp8r.dll and vfp8t.dll. Of course, I need to know for sure what DLLs my application might need to run every function, so I guess I will at least revisit Installshield to see what DLLs it will try to install. In general, however, Installshield has been a headache and I would prefer to just use Inno Setup 4. Is there an easy way to know what DLLs are required for a VFP8 application?
>
>Also, why can't I manually register gdiplus.dll, msvcr70.dll, and vfprenu.dll and avoid the invalid entry point errors?
>
>I have tried this on an XP SP1 PC and a WIN2K PC and I get the same error no matter what version I use and how I do it.
>