>>>>I'm having a problem deploying an ActiveX control on my form using the "OBJECT" tag.
>>>>
>>>>I want to run an ActiveX control on hte client-side that is gotten from the server-side. I've tried the codebase parameter but have had no luck... Does this require me to use a .cab file or can you deploy the control by just pointing at it?
>>>>
>>>>Is there a way to create an instance of a control on the client when the control resides on the server?
>>>>
>>>>Thanks for any help...
>>>>Michael
>>>
>>>Yes, this is what DCOM does. The client machine has to know the location of the server's control. You configure this and additional security settings with DCOMCNFG.
>>
>>Does that mean I have to configure each client, or configure the server to tell each client where to look?
>>
>>Thanks...
>>Michael
>
>You have to configure each client. There is probably a way to do this programmatically, but I don't know how. Ed?

It's not too difficult; there's actually good documentation on a relatively simple approach using the Windows Scripting Host in the MSDN docs under the topic DCOM, registration element, which includes sample VBScript for registering both local and DCOM components using scripting. The MSDN documentation can be found on-line at msdn.microsoft.com, and I think is also available in the currently downloadable documentation on the WSH, as a part of the Script Component Tutorial.

WSH makes life much easier... < g >