>>>I know I need to have the setup program register my OCX controls, do I also need to have the setup program register the support DLL's? Some of the DLL's that need to be distributed according to the OCX vendors are:
>>>
>>>MFC40.DLL
>>>MSVCRT40.DLL
>>>MSVCRT20.DLL
>>>MSCANS32.DLL
>>>STORAGE.DLL
>>>TYPELIB.DLL
>>>OLE2.DLL
>>>OLE2DISP.DLL
>>>OLE2NLS.DLL
>>>COMPOBJ.DLL
>>>COMDLG32.DLL
>>>
>>>Do I just have setup copy these files to the WINDOWS\SYSTEM directory (overwriting only if older version) without having REGSVR32 register them?
>>>
>>>I know for the most part most of these files will already be on the users machine, but I cannot know for sure since this application is being distributed to over 600 sites.
>>>
>>>Any help along these lines would be greatly appreciated. I just didn't want to leave something out before distributing to all these sites.
>>>
>>>TIA,
>>>
>>>James
>>
>>Almost all of these DLLs (not sure about MSCANS32.DLL only) would be even distributed with plain VFP application, so you probably shouldn't worry about them at all. I think you could first run Setup Wizard to create distrib package w/out Active-X and see what dll you already catch.
>
>Thanks - Ed,
>
>I am currently using PC-Install to distribute this application. Maybe it would be a good idea to first setup in VFP Setup Wizard to see what files the Setup Wizard sets up for registering!? I tried Setup Wizard several months ago and don't recall anything being setup to be registered, just copied. So maybe I don't have to worry about the above DLL's with regards to having PC-Install register them, just make sure they are copied to WINDOWS\SYSTEM directory (only if newer version). Would you agree?
>
>James

I can say nothing about PC-install, but I guess, that the right way is to try installing on 'brand-new' machine and see how the app will work.