TIMEOUT and COM : HELP !!!

[eric33]

I make an activeX control under VB.
This one call another activex.

I make an app that call my vb ocx.
To resume the app call vb's ocx that call another ocx.

If the process of the last activex (called by VB ocx) is too length (depending of the machine speed) i have a message that appears and says :

Title : Server Busy
Text : This action cannot be completed because "name of ocx called by vb ocx" program is not responding. Choose "Switch to" and correct the problem.
Buttons : Switch to ..., Retry, Cancel (grayed)

But in fact all is ok. If i wait and click on retry all is ok.

This is like a system timeout on either vb ocx call or com system call.
I dont know if it is a system message or a vb sdk message.

I want to avoid this type of message.

Could your help ???

[Lothar Haensler]

there is an OLEServerBusyTimeout property that you can set for the application object.
Check out the online docs.

[eric33]

Fine this is what i need but the problem is that function dont works in a ocx.
The error is : Operation not valid in ocx dll.

In fact the problem is that i have an app that call a vb ocx that call another (generic) ocx.
I want to avoid timeout on the last ocx.
The better way is to implement OLEServerBusyTimeout in the first caller that means my app.
But this app is a MFC app (visual c) not a vb app.
Dont know how to implement the timeout in my mfc app.