Recent content by Rick1972

There is an API (CopyFileEx) which uses a callback function to allow you to follow the progress of the copying.

I once wrote a VB addin, which processes one of the currently opened projects in the IDE. This way you have error handling everywhere you want it, without having to write your handlers by its own. Just make sure you include sections of where you are sure that may raise errors during application...

The choice of starting a new instance or use an already running instance of a COM server lies in the architecture created by the programmer of the COM server. You as a client cannot determine whether or not you will get a completely new instance of the server. Otherwise it wouldn't be of much...

I am sorry then, I would have to see for myself then... But I cannot create the project right now (I think my boss would not like this very much doing that in his time). It seems to me that somehow the DCOM configuration on your server computer has gotten messed up... What if you tried to...

Are you now still getting any messages on the server machine (in the log I mean)? And maybe this is a redundant question, but did you now also execute MyServer.exe /regserver on the server machine?

Have you tried registering the server app on the client machine the same way you did on the server machine (i.e. Myserver.exe -regserver) ?

I think it is not properly registered then on your client machine...

You probably do not get any DCOM errors in the log because DCOM is not being used when working locally. Which error message did you get when trying locally?

The parent constructor is automatically called when you create a new instance of your child class. If you explicitly want to change the constructor being called in the parent class, you can do thus by entering : XXX(x,y, etc...) before the opening bracket of your child's constructor (where XXX...

Does it work locally ?

I am not sure how to register a typelib manually. You place a copy of your server on the client and register this (just for the test). You can also browse with VB to your typelib and set a reference to it, but just to be safe try the first option (if this does not work then it is not necessary...

The client app need not be registered. have you also registered the server app manually at the client machine? COM needs to know where to find the typlib to marshall your calls.

Go to the correct path, type the name of your server with argument regserver; i.e: MyServer.exe -regserver

I am not sure, I have not used the pdw for a long time now. Can you not just manually register the server app on the server machine and see what happens?

Did you check all registry settings on both the client and the server (i.e. is there maybe an interface pointing to a non-existing typelibrary, or a typelibrary pointing to a non-exeisting path etc.) ?