hi,

i have an activex-exe created in VB6

i use the component in a website with ASP

i can perfectly use the component on my own computer

but now i want to move the website to my webserver and

  leave the component on my own pc



to use the component (remotely) i registered the component

  on the webserver (i can find the CLSID in the registry)

i did this by running the activex-exe, which is shared on the network



now, when the ASP-page (that uses the component) is called,

  it generates an error "couldn't create activex-object"



at the moment the component is registered on a WIN2K machine

but it's supposed to run on WIN98



can anyone help me, plz



all help is appreciated

Tom Verhelst

I'd like to help, but I'm a little confused about your setup.



First off, you say you have a activex-exe. Then say you are using a

component.  What's the story?

The important part, as far as the webserver is concerned is that you have a

component (DLL).  This DLL should reside and be registered on your web

server. I would think that it's pretty dangerous to try to use a DLL that's

accessed over a network.



Here's what I recommend:

-Put the DLL that you created on the Webserver.

-Register that DLL. (I'm not real sure what you mean when you say that you

registered the component by running the activex-exe) You made need to (and

it's recommended) unregister the previous DLL).



Peter L

So why isn't an ActiveX.exe a component??



DLL's are 'In-Process' components and normally run in the same process space

as the calling application.



ActiveX.exe are 'Out-Of-Process' COMPONENTS and run in a seperate process

space from the calling application.



Either can be called and used from a different / seperate server over a

network, local or otherwise.

Dangerous?? I think Microsoft would disagree with you on that, what do think

DCOM is all about?



As for Tom's initial question, well here I fail I'm afraid. Not too sure

about the backwards compatability of the object from Win2K to '98. My only

suggestion is have you tried calling it on another Win2K machine to rule out

this cause?



Geoff



> Subject: RE: out-of-process component using over LAN

> From: "Peter Lanoie" <planoie@e...>

> Date: Fri, 16 Feb 2001 15:29:29 -0500

> X-Message-Number: 7

>

> I'd like to help, but I'm a little confused about your setup.

>

> First off, you say you have a activex-exe. Then say you are using a

> component.  What's the story?

> The important part, as far as the webserver is concerned is that you have

a

> component (DLL).  This DLL should reside and be registered on your web

> server. I would think that it's pretty dangerous to try to use a DLL

that's

> accessed over a network.

>

> Here's what I recommend:

> -Put the DLL that you created on the Webserver.

> -Register that DLL. (I'm not real sure what you mean when you say that you

> registered the component by running the activex-exe) You made need to (and

> it's recommended) unregister the previous DLL).

>

> Peter L

>

> ----------------------------------------------------------------------