Keeping Access Running Between SQL Server Reboots

[W]

We have a Microsoft Access application that terminates with an error every
time SQL Server is restarted. My understanding from Googling this is that
either the application or the driver is using database
queries / connections that become invalid as soon as SQL Server stops. Is
there any driver we can use with Access that would implement a connection
pool or some mechanism behind the scenes that would allow Access to survive
an SQL Server reboot?

 

[Lutz Uhlmann]

Am 24.06.2013 10:02, schrieb W:

We have a Microsoft Access application that terminates with an error every
time SQL Server is restarted. My understanding from Googling this is that
either the application or the driver is using database
queries / connections that become invalid as soon as SQL Server stops. Is
there any driver we can use with Access that would implement a connection
pool or some mechanism behind the scenes that would allow Access to survive
an SQL Server reboot?

You should ask this to the developer of your application.

I think the application runs into a timeout during communication with
your sql server.
Maybe you can change default timeout for sql connections to a higher
value. But it doesnt work, if the application use it own timeout values.

 

[W]

Am 24.06.2013 10:02, schrieb W:

You should ask this to the developer of your application.

I think the application runs into a timeout during communication with
your sql server.
Maybe you can change default timeout for sql connections to a higher
value. But it doesnt work, if the application use it own timeout values.

Our developers cannot find a workaround.

We think the Access driver is using a connection pool, and when SQL Server
reboots that connection pool can no longer be relied on and returns a
permanent error that breaks Access.

We are hoping there is an alternate driver, or a programming approach, that
might work around this.

 

[Gloops]

W wrote, on 28th June 2013 14:59 UTC + 2 :

Our developers cannot find a workaround.

We think the Access driver is using a connection pool, and when SQL Server
reboots that connection pool can no longer be relied on and returns a
permanent error that breaks Access.

We are hoping there is an alternate driver, or a programming approach, that
might work around this.

Hello, what was done as error procedures ?

--