>Of course the next logical question is what is the proper way to install those controls.

Installation of an OLE component (ActiveX control or OLE Automation server) is pretty simple. there are two basic steps:

(1) Ensure that any shared components such as common .DLLs referenced by the OLE component are in place on the system. The files need to be located on the Windows search path, and may themselves require registration. In most cases, the common components will need to be placed in the Windows System directory.

(2) Invoke the self-registration code in the component. There is a utility REGSVR32.EXE which can do this for you, or it can be done programmatically within an application. Doing this creates or updates entries in the Windows Registry needed to locate and use the control.

If REGSVR32.EXE is located anywhere on the Windows search path, you can invoke it against a file from a command prompt, within a batch file, or from the Start Menu/Run box by the command REGSVR32 name of file to register. For example, to register the ActiveX control MyControl.OCX located in C:\MyApp, you'd use the command:

REGSVR32 C:\MyApp\MyControl.OCX

There is an example of programmatically registering a file within a VFP app in the FAQ.

>
>I downloaded the setup wizard repair, and have SP3 installed on all systems. I did a lot of programming 10 years ago, but much of the termonology has changed since I was active in programming. I'm not sure where or how to "register" those controls.

You need to rebuild the installation set once the Setup Wizard update is in place. You need to tell Setup Wizard which of your files are ActiveX controls so that Setup Wizard will register them in Step 6 Change File Settings of the Setup Wizard - there's a grid listing the files in your distribution set, and you need to ensure that any ActiveX controls are marked as such (check the box marked ActiveX for each ActiveX control that you include) so that Setup Wizard will register them.