>How do I check the registry? Shouldn't the setup wizard register what is sneed upon installation of the distribution disks (that I created for the app)?

The Setup Wizard only puts on things that you tell it to - it doesn't automagically go out and grab other files off your system, since you may not have a legal right to redistribute them. If you've marked a File as an ActiveX component in the Setup Wizard dialog, and it fails to register properly, you should get an error message back from the install, but if you ran the install silently or ignored it, it simply is not that smart to know that you blew the installation.

If you haven't marked the file as an ActiveX component through the dialog, VFP doesn't know it needs to register it, and as a result, it doesn't even try. Copying files is not an adequate install in many cases, and you need to either have Setup Wizard register it for you and pay attention to any failures, or take responsibility for it yourself.

You can check the registry by hand using a tool like REGEDIT; VFP6 includes a registry manipulation class as a part of the FFC, and there are registry manipulation classes available for download here on UT from the Files section for earlier versions. To check if this key exists using the VFP6 FFC class, the following would work if you include the necessary .H, .VCX and .VCT file in your project:

SET CLASSLIB TO Registry ADDITIVE  && needs REGISTRY.VCX, REGISTRY.VCT
#INCLUDE REGISTRY.H  && and obviously the .H file, too!
oReg = CREATEOBJ("Registry")
IF oReg.OpenKey("<i>fill in the name of your automation server</i>")
   *  the registry key exists - by default the FFC goes against HKEY_CLASSES_ROOT
   oReg.CloseKey()
ELSE
   *  it doesn't exist
ENDIF
oReg = NULL