Automation Error

[LeoHart]

Hi,

ever so often I receive the following error in my application:

-2147417848 Automation Error. The object invoked has disconnected from its client

The error is happend randomly so I have been unable to identify what is happening. Does anyone know what this error means and how I can work around it.

Many thanks,

Leo

[agent]

If you're doing what i'm doing (writing an ActiveX EXE and DLL at the same time with two instances of vb) you'll need to unreference the activex exe from dll each time you change the exe.

When you start the exe, then you can refence it from the dll (until you change the exe again.)

If this is not what your doing then, i have no idea how to help you here.

[LeoHart]

Many thanks for your reply.

To clarify, The application I have written is an OCX which is placed on an ActiveX exe. The OCX references 2 DLLs. None of my components reference the AxtiveX exe. All access to the DLL are initiated via the OCX.

Any ideas???

Thanks again,

Leo.

[Abashai]

Well this is a known bug
You will need to install service pack 5. At least this is what Microsoft says.

[veryjonny]

Sorry to have brought this thread up, But I am getting the same error. I am using no dll's or ocxs and the OS is Xp. then too I get this error. If someone has found a soln or a reason , Kindly post it back.

[Stiletto]

This error happens couse your program or one of your objects is referencedto another, and when it runs, it can't 'open' the referenced object by its own.

For example, you take a test program and a test ActiveX exe, and you reference the AX with teh program, and you put code which tells the ActiveX to run.
You run the program, click on the command button which runs the code which suppose to run the AX, but if u'll try it u'll see it aint workin, cuz the ActiveX cant run itself. you will need to click the 'play' button in the AX and only then you will be able to run the AX from the program, since the AX is already running.
Hope I helped...