A simple com problem

[Kirun]

have made a sinple component dll in vb . . with a
public sub ...
showing a message box..
i instantiate it through vb .. client . .
working fine ..
but when i do instantiate in asp by
server.createobject ..
it doesnot work . .
i debugged .. its successfully loaded but.. when
calling proc .. its getting hanged...
but the irony is that .. its working fairly on my
other pc wid pws..
tell me if it is IIS prob. .
means when i installed a component ..
plz tell what u understand and what we can do of it .

[WALDO]

Let's see...

Q - If you're running the DLL on your machine, which is running PWS, where does the messagebox appear?

A - On your machine. Why? Because your machine is acting as the server AND the client so you can't tell the difference.

Q - If you're running the DLL on your server and viewing the ASP page on a different machine (your client), where does the messagebox appear?

A - On the SERVER!!!! Why because that's where the DLL is running!!! You can't MsgBox from Active SERVER pages. The message box pops up on the SERVER and your DLL remains frozen until someone clicks OK on the SERVER!!!!

[jjortiz]

It's not going to work. Because it's server side and the dll is not going to support msgboxes once it's compiled. I think in this case what you need to do is go into Project properties and check unattended.

[MarkT]

I'm a little fuzzy here, but I believe what is going on it that the dll is being created on the server and when it produce a message box it is displayed on the server and you never see it. If you are making a component that is supposed to run remotely, it should have no user interface (a message box).

[jjortiz]

Also when you place the msgbox in there. In win2k or NT what it does it reports it the Event log.

[WALDO]

Right on the money