Hi Mat,

you have to run your setup from Add Programs, not by clicking the exe. This, in turn, creates a dummy registry entry. When the program runs, under a user, the call to the activex goes against the registry; if the class cannot be found, the dummy registry is searched, and the class is registered for the user during that first call (it is present from then on).

Your setup has to run "for all users of this computer" of course.

You can also do this by issue commands from the CMD window setting TS into administrative mode; and if doing manual regsvr, in fact have to do it this way. But the easiest way is to run an install which works for a workstation but using the Add Program method.

hth,

Hank

>I have a company that has recently deployed my application in a Terminal Server environment. When the Admin runs the .exe, everything is fine, but if any of the users try to launch a form with an aciveX control they keep getting the message that the activeX control is not registered.
>
>The controls in question are mscomctl.ocx and mscomct2.ocx. The Admin has tried to run REGSVR32 for each of the controls and the system says they are registered.
>
>Has anyone seen this behavior before and have an idea how to solve this? Thanks in advance for any help.
>
>
>Kind Regards,
>
>Mat