Do not crash when DB connection lost

[dserodio]

When the DB connection closes, for instance because of a timeout (I went to lunch), EA crashes and dies.

It would be really nice if it tried to reopen the DB connection before giving up.

[alexander]

Second that, we also had a latency issue with a db in our datacenter and EA would actually crash while attempting to open the project.
No tweak in the connection timeout or any other options seemed to solve this.

[Bruno.Cossi]

On a somewhat related note, a bit of optimization of the communication between the EA application and the database would be nice, too. The bandwidth required between the app and the db is huge, I guess a lot of data gets moved between the client and the server repeatedly and therefore inefficiently.
It is virtually impossible to use EA with a remote database. Applications where one would expect much more data being moved between the client and the server, handle this with no problem.

I suppose this would require rewriting the whole application though, so I will keep this at the very botoom of my wish list.

Bruno

Second that, we also had a latency issue with a db in our datacenter and EA would actually crash while attempting to open the project.
No tweak in the connection timeout or any other options seemed to solve this.

[Paolo F Cantoni]

Bruno,

Is this true of "repository" based databases or just the EAP file.

If you're experiencing it with an EAP file, then it's probably the way MS Access works.  It's not a true "server".  If its happening with SQLServer or orne of the other DB repositories then it's a more general EA design issue.

I'm one of MS Access's greatest fans, but one must realise its limitations in some circumstances.

Paolo

[Bruno.Cossi]

Paolo,

this is happening with MS SQL as well as Oracle databases.

Bruno

Bruno,

Is this true of "repository" based databases or just the EAP file.

If you're experiencing it with an EAP file, then it's probably the way MS Access works.  It's not a true "server".  If its happenning with SQLServer or orne of the other DB repositories then it's a more general EA design issue.

I'm one of MS Access's greatest fans, but one must realise its limitations in some cercumstances.

Paolo

[kelly_sumrall]

I would also like to see this handled better. Here is a response I got from a member of support when I reported this as a bug

This is by design. When EA detects a network failure, it will warn the user and then shut down. I'd suggest you save and close EA before unplugging the network cable.

It wasn't a very helpful design to have the application give an informative message then die during a presentation to my managers after moving my laptop from my desk to the coference room (and reconnecting to the network).
Replication is really the solution, but the application should not give up the ghost so easily without a fight.

[alexander]

If it would crash only when disconnecting the network cable it would be understandable, but even with a peak of network traffic it falls down horribly.

We are also using SQL2000 and having the same problems. I have determined it is a latency problem because when we moved the database to a SQL2000 server in our subnet (to discard a server problem) the problem dissapeared, and the database was running because when using enterprise manager client we could access it perfectly.