Hi,

I also had the same problem like u do, however, even when I had my ocx and dll files placed in the same directory as my executable, my setup installation still had error of ocx cannot be register successfully leaving me without any program group setup in the win95/win98.

In addition, what happen if the OCX or DLL files that we are using is older that what our customers have, do the installation setup by vfp 5.0a prompt us about ?

Thank a lot.



>Hi Nancy,
>
>I checked out the Microsoft Knowledge Base and found an article that took care of my problem and thought I would tell you about it in case you are having the same problem. The article # is Q160771. Basically it says the .ocx file needs to be in the same folder as the executable in your distribution tree. I had my ocx in a subfolder called libs...as soon as I moved it into my app root directory in the distribution tree my problem went away. I hope this helps...Let me know.
>
>Paul
>
>>To add to my reply...
>>I also change the installation directory of the OCX to be my application directory--so I know where to register the darn thing. An OCX doesn't _have_ to be in the Windows directory path. (This wasn't obvious to me)
>>
>>>1. Include the ocx in my distribution directory
>>>2. Uncheck the ActiveX mark that gets set automatically during the setup wizard
>>>3. Run, as a post-setup up executible REGSRV32.EXE blah blah blah.

Best Regards
Virusim