About using the MSysConf table to optimize your linked SQL database (MDB) - Access

Click here to switch to other Office Online sites worldwide

United Kingdom (change) | All Microsoft Sites

	Microsoft Office Access

Search

	Word 2007 Outlook 2007
Get up to speed

	Get your business online Get help using Office 2007
Your business

	Check for free updates
Office updates

Microsoft Office Access

» Access Home

Product Information

» Overview

» Top 10 Benefits

» See it in Action

» Compare Features

» Try Now

» Buy Now

Help and How-to

» Access 2007 Help

» Access 2003 Help

» Access 2002 Help

» Access 2000 Help

Choose your version

Training

» Access 2007 Training

» Access 2003 Training

» Access 2007 Demos

» Access 2003 Demos

Templates

» Templates for Access

Support and Feedback

» Product Support

» Send Us Your Comments

Technical Resources

» Developer Center

» Office Resource Kit

Additional Resources

» Office Marketplace

» Discussion Groups

» Access Solutions

» Access MVPs

Home > Products > Access > Access 2003 Help and How-to > Working with Data > External Data > Importing and Linking Data or Objects

Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.

Printer-Friendly Version

About using the MSysConf table to optimize your linked SQL database (MDB)

Applies to: Microsoft Office Access 2003

Note The information in this topic applies only to a Microsoft Access database (.mdb).

Important If you create an MSysConf table, it must be set up properly or you will not be able to connect to the SQL database (SQL database: A database that is based on Structured Query Language (SQL).) table at all.

If you are administering an SQL database that uses Microsoft Access as a front end, then you can create a table in your SQL database named MSysConf to help you control communication between the two applications. The MSysConf table has two potential functions:

It can disable the feature that enables users to save the logon ID and password for a linked SQL database in the Microsoft Access front end.
It can optimize how Microsoft Access performs background population of records during idle time by setting the number of rows of data that are retrieved at one time and the number of seconds of delay between each retrieval. Microsoft Access uses a default of 100 records that are returned every 10 seconds if you don't create the MSysConf table.

Show The structure of the MSysConf table

The SQL database table MSysConf should have the following structure.

Column name	Data type	Allows Null?
Config	A data type that corresponds to a 2-byte integer	No
chValue	VARCHAR(255)	Yes
nValue	A data type that corresponds to a 4-byte integer	Yes
Comments	VARCHAR(255)	Yes

Note If the data source you're working with is case-sensitive, then use the table and column names exactly as shown.

Show The data in the MSysConf table

There are three valid records in the MSysConf table. The following table shows what values you should enter in the Config and nValue field. The other columns are reserved for future use, and their contents are ignored.

Config	nValue	Meaning
101	0	Don't allow local storage of the logon ID and password in linked tables.
101	1	Allow local storage of the logon ID and password in linked tables.
102	D	D is the delay in seconds between each retrieval.
103	N	N is the number of rows retrieved.

Note Setting a higher delay time decreases network traffic, but increases the amount of time that read-locks are left on data (if the server uses read-locks).