This was a common problem with old ActiveX controls, that is, those that were supplied with VFP 5.0 and earlier. It simply means that the control is not properly registered. You can usually solve it by registering the control on the target system, which can be done as part of your setup program, or by executing REGSVR32.EXE (which you run from the command prompt, passing the path and name of the ActiveX control (the OCX file) as a parameter).
In fact, a much better solution is to use a more up-to-date version of the control. In general, the controls that come with VFP 6.0 are more reliable.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.