Nope - nothing wrong with your com component - it's kinda slick actually.

No - it's probably because you haven't registered your com component on your NT workstation .. try this ...

If you haven't done so already - copy the component server .exe or .dll over to your Windows NT workstation and place it in c:\winnt\system32.

Then register it like this ...

regsvr32 mycomponent.dll

or

mycomponent.exe /regserver

You should get a messagebox saying the component was registered.

Then check for a registry key called HKEY_CLASSES_ROOT\SERVEUR001.REVERSE - if it exists - your component was registered.

Then re-run your script ...

My guess this time is ... ummmm ... it'll work perfectly from here on in !

Unless of course - this is a remote com object (DCOM) - in which case you have to go through another process - let me know ...

Shawn.

By the way - it's good to see other's with an interest in writing com objects for kix - whatcah up to ? - anything that may be of interest to "da-board" here ?

Shawn..

[This message has been edited by Shawn (edited 25 October 2000).]