>>I'm now trying to use another Software to generate installation disks, but I couldn't implement the ocx files registry.
>>
>>Looking at some previous messages, I have found out something about REGSRV32. Is that the answer? If so, where should be located this file? And how exactly should I use it?
>>
>>BTW, is there any tip to check via program if a specific OCX file is registered or not (it could avoid some GPFs...)
>
>If you're not using a third part installer that offers support for self-registering .ocx files, bet one, and ditch the product you're using. You're asking for more trouble than its worth otherwise.

Hi David, thank you for answering!

Do you have any suggestions about a third part installer? (If so, where can I find it?)

>If you insist on doing otherwise, a call to REGSRV32.EXE *may* do the trick, depending on when it is called. The syntax is simply
>
>regsrv c:\windows\system\myocxfile.ocx

Just don't know in which moment and how I could run this command automatically during the installation (I guess a post-executable written in Vfp wouldn't run because of Vfp5000.DLL...)

>(you did copy the .ocx to WinSys, didn't you?)

At least this is working fine...

>However, there are a number of dangers to this, and I *strongly* recommend using a third-party installer that can handle this work, instead.
>
>You can check search the Registry for references to your .ocx, simply by searching on the file name (it's the cheater's method, but it works). Make sure you make no changes to the Registry when you do this - otherwise your machine may become UNBOOTABLE.

Taking this opportunity, which one is the registry file?

Thanks again,

Renato