Keeping Access Running Between SQL Server Reboots

Discussion in 'Access General' started by W, Jun 24, 2013.

  1. W

    W Guest

    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?
     
    W, Jun 24, 2013
    #1
    1. Advertisements

  2. W

    Lutz Uhlmann Guest

    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.
     
    Lutz Uhlmann, Jun 24, 2013
    #2
    1. Advertisements

  3. W

    W Guest

    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.
     
    W, Jun 28, 2013
    #3
  4. W

    Gloops Guest

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

    Hello, what was done as error procedures ?

    --
     
    Gloops, Jun 28, 2013
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.