When you are raising an error from your VB Server, your server
momentarily becomes a client, and the client behaves as a server. In
this case, your "server" has disappeared.

As a VB "client", you can control the behavior you describe by altering
the OLERequestPendingTimeout property.

Have a look at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon98
/html/vbconchangingserverbusymessage.asp

(watch out for line breaks)

> Hi,
> I have a problem:
> I developed a DCom Server in Vb.
> This server have to monitor the status of some data stored in a
database
> and
> then raises event sincronously to some client.
> The problem is when a client disconnect abnormally, the server raises
all
> the events with delay, and the message "The server is busy....Switch
> To-Retry" appears.
> This cause me a lot of problem, because I need to take the events in
time.
> Is there a way to workaround this problem?
> Thanks in advance.
>

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]