• Microsoft Access Odbc Error 3151
• Microsoft Access Odbc Driver
• Microsoft Access Odbc Connection Error
• Odbc Connection To Database Failed
• Ms Access Error Odbc Connection Failed
• Microsoft Access Error Odbc Call Failed

Active3 years, 9 months ago

There is a MS Access application with tables on MS SQL Server linked through ODBC. When connection is lost i receive ODBC error 3146. After connection is restored physically i still receive ODBC 3146 errors. I have to make something like a reconnect to server. How can i do this in MS Access?

For more information about a problem that occurs when you use ODBC Driver for DB2 to access an IBM DB2 table that has a column name that is 30 characters long, click the following article number to view the article in the Microsoft Knowledge Base.

Sep 17, 2018  Note This issue may also occur when you try to open the linked table from other applications that are connected to the SQL Database instance table by using Microsoft Open Database Connectivity (ODBC). When you create the ODBC connection to SQL server, select the option of With SQL Server authentication using a login ID and password entered by the user. Also, confirm that in Microsoft Access, the Machine Data Source and System Data Source has been used to create the ODBC connection.

host.13host.13

2 Answers

I think all you need to do is refresh the table links. Are you asking how to relink the tables programmatically? Have you tried refreshing the links after being disconnnected and verified that it solves the problem? Refreshing the link in VBA would be something like

You may have to loop thru the tables to get the index I am not sure if it will take the table name but you could try it that way first.

Gord Thompson

83.1k1616 gold badges110110 silver badges247247 bronze badges

BPCSBPCS

Where is your Access table in reference to your SQL Server? If your Access table is local and you are the only one using it then refreshing table links is sufficient. However, if the Access db lives on a server or some other shared space where many people are using it they will not be able to access the SQL tables if you are using a USER DSN. Setting up a system DSN or a dsn file will provide Access with the information it is looking for as to where the SQL tables are.

TSSTSS

Not the answer you're looking for? Browse other questions tagged ms-accessodbcdatabase-connectionaccess-vbareconnect or ask your own question.

Open Database Connectivity (ODBC) is a protocol that you can use to connect a Microsoft Access database to an external data source such as Microsoft SQL Server. This article contains general information about ODBC data sources, how to create them, and how to connect to them by using Microsoft Access. The procedure steps might vary depending on the specific database products and ODBC drivers used.

In this article

About ODBC data sources

A data source is a source of data combined with the connection information that is required to access that data. Examples of data sources are SQL Server, Oracle RDBMS, a spreadsheet, and a text file. Examples of connection information include server location, database name, logon ID, password, and various ODBC driver options that describe how to connect to the data source. This information can be obtained from the administrator of the database to which you want to connect.

In the ODBC architecture, an application such as Access connects to the ODBC Driver Manager, which in turn uses a specific ODBC driver (for example, Microsoft SQL ODBC driver) to connect to a data source. In Access, you use ODBC data sources to connect to data sources external to Access that do not have built-in drivers.

To connect to these data sources, you must do the following:

• Install the appropriate ODBC driver on the computer that contains the data source.
• Define a data source name (DSN) by using either the ODBC Data Source Administrator to store the connection information in the Microsoft Windows registry or a DSN file, or a connect string in Visual Basic code to pass the connection information directly to the ODBC Driver Manager.

Machine data sources

Machine data sources store connection information in the Windows Registry on a specific computer. You can use machine data sources only on the computer they are defined on. There are two types of machine data sources — user and system. User data sources can be used only by the current user and are visible only to that user. System data sources can be used by all users on a computer and are visible to all users on the computer and system-wide services. A machine data source is especially useful when you want to provide added security, because only users who are logged on can view a machine data source and it cannot be copied by a remote user to another computer.

File data sources

File data sources (also called DSN files) store connection information in a text file, not the Windows registry, and are generally more flexible to use than machine data sources. For example you can copy a file data source to any computer that has the correct ODBC driver so that your application can rely on consistent and accurate connection information to all the computers it uses. Or you can place the file data source on a single server, share it between many computers on the network, and easily maintain the connection information in one location.

A file data source can also be unshareable. An unshareable file data source is contained on a single computer and points to a machine data source. You can use unshareable file data sources to access existing machine data sources from file data sources.

Connect strings

Microsoft Access Odbc Error 3151

In a module, you can define a formatted connect string that specifies connection information. A connect string passes the connection information directly to the ODBC Driver Manager, and it helps simplify your application by removing the requirement that a system administrator or user first create a DSN before you use the database.