Connection to database server

[Anthony]

We have a split database with a client front end and a back end that has the
tables. The back end is on a remote server that we must connect to when we
sign on to the database. We connect to the MS SQL server using ODBC. Since
we use the database in traveling around the country, we have programmed the
database to allow us to temporarily move the back-end data onto our C-Drive,
just in case we don't have ODBC connectivity we would still be able to use
the database. Of course, it only gives us a "snapshot" of the data.
One of the issues that has come up is the database tries to connect to the
SQL Server on startup even if we have moved the data to our C-drive. When we
are in the hinterlands, it can take a few minutes of trying before knowing
we don't have a connection and allowing us to use the C-drive data.
Of course, we can program a checkbox that tells the SQL server, "don't look
for a connection" when we sign on. I am wondering if there is a more
"elegant" solution. Is there a way for ACCESS to "instantly" know if we have
network connectivity, and therefore, not even look for a connection?
Thanks for your advice.

 

[Maurice]

I don't think that using a radio button or check box is not a elegant
solution. Many databases use a login window which ask the user if they want
to connect to the server or just want a local login. In code you can check
the radio or check to see what the user wants and connect accordingly. Seems
like a good solution to me...

 

[Anthony]

Thanks for your response. Going the radio button route might just be the
most programmatically straightword route. However, I was trying to create a
"smarter" database that would automatically recognize the network, then maybe
ask if you would like to connect.