I have a EDB 2.03 Build 14 and Delphi 2007.

In my application, I support the users having the database on a network folder.

If the network connection goes away (for whatever reason), and the user then tries to pull up another record, they get an error. Makes perfect sense.

When the network connection comes back, they can continue using the software normally.

Except for one thing: When they go to close, the EDB Engine starts throwing exceptions.

Specifically, any attempt to set a session's Connected propery to False, including just freeing the data module with the session component, gets the error: "The specified network name is not available" This seems to happen because the engine or the session or someone still thinks the network connection is gone, even when database components and tables recover and work fine.

Is there some procedure or function that will force the session component to "Look again, and reconsider" the state of the network?

Thanks!

-David

David,

<< Is there some procedure or function that will force the session component
to "Look again, and reconsider" the state of the network? >>

Unfortunately, no.  The issue is that, once the network connection goes
down, all of the file handles, etc. are now invalid as far as the OS is
concerned, and there's no way for ElevateDB to re-establish them without
shutting everything down and re-opening all of the network resources/files.
Plus, there's the added issue of being able to detect a transitory failure,
as opposed to a permanent failure (how long to wait, etc.).

--
Tim Young
Elevate Software
www.elevatesoft.com

I was hoping that since the database and table components can recover when the network comes back that the session could, as well.

Ah, well, so it goes sometimes. I'll see what I can come up with.

Thanks.

-David