odbc - call failed: communication link failure

[Florin]

Hi!
I have an Access front-end (MDE, Access 2007) linked to a SQL Server
back-end (SQL Server Express 2008).
If for whatever reason the network communication goes bad I get the error
"odbc - call failed: [...] communication link failure".
This crashes the entire front-end. No matter if the communication is
restored one millisecond after, once the error comes up I have to restart
Access in order to be able to work again with it.
Is there a way to trap that error?
I would like to simply bring a screen up "Communication with the server is
interrupted" and block access to the front-end.
Then when the communication works again I'll allow back the access to the
front-end.
Any thoughts?
Thanks!
Florin

 

[Sylvain Lafontaine]

If your network is not rock solid then you'll should use Remoting (Single
Session, Terminal Server, Thinsoft, etc.) to access your application over
the network on a remote desktop session.

A second possibility would be to install a local instance of SQL-Server
(probably the Express Edition) and set up Replication or Synchronisation
between it and the backend server.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Florin]

Thanks Sylvain.
Do you mean there's no way to trap the ODBC error?
I was thinking maybe in the OnError event of the forms.
Your thoughts?
Thanks!
Florin

If your network is not rock solid then you'll should use Remoting (Single
Session, Terminal Server, Thinsoft, etc.) to access your application over
the network on a remote desktop session.

A second possibility would be to install a local instance of SQL-Server
(probably the Express Edition) and set up Replication or Synchronisation
between it and the backend server.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

Hi!
I have an Access front-end (MDE, Access 2007) linked to a SQL Server
back-end (SQL Server Express 2008).
If for whatever reason the network communication goes bad I get the error
"odbc - call failed: [...] communication link failure".
This crashes the entire front-end. No matter if the communication is
restored one millisecond after, once the error comes up I have to restart
Access in order to be able to work again with it.
Is there a way to trap that error?
I would like to simply bring a screen up "Communication with the server is
interrupted" and block access to the front-end.
Then when the communication works again I'll allow back the access to the
front-end.
Any thoughts?
Thanks!
Florin

 

[Sylvain Lafontaine]

To my (limited) knowledge, no. This is a question that comes often,
especially when the SQL-Server is on a cluster (changing the active node
will have the same effect) and I don't remember having ever seen an adequate
answer to that.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

Thanks Sylvain.
Do you mean there's no way to trap the ODBC error?
I was thinking maybe in the OnError event of the forms.
Your thoughts?
Thanks!
Florin

If your network is not rock solid then you'll should use Remoting (Single
Session, Terminal Server, Thinsoft, etc.) to access your application over
the network on a remote desktop session.

A second possibility would be to install a local instance of SQL-Server
(probably the Express Edition) and set up Replication or Synchronisation
between it and the backend server.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam
please)
Independent consultant and remote programming for Access and SQL-Server
(French)

Hi!
I have an Access front-end (MDE, Access 2007) linked to a SQL Server
back-end (SQL Server Express 2008).
If for whatever reason the network communication goes bad I get the
error
"odbc - call failed: [...] communication link failure".
This crashes the entire front-end. No matter if the communication is
restored one millisecond after, once the error comes up I have to
restart
Access in order to be able to work again with it.
Is there a way to trap that error?
I would like to simply bring a screen up "Communication with the server
is
interrupted" and block access to the front-end.
Then when the communication works again I'll allow back the access to
the
front-end.
Any thoughts?
Thanks!
Florin