ACC: System Tables and Conflict Tables Are Not Replicable

 Last reviewed: June 5, 1997
Article ID: Q141042
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

In Microsoft Access 7.0 and 97, system tables and conflict tables (tables that contain database records that conflicted during the synchronization of two replicas) may not be made replicable by Microsoft Access. The reason for this is that system tables are created for each database upon creation (replication).

NOTE: Although you can create a replica of a system table using Visual Basic for Applications code. It is not recommended.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open the sample database Northwind.mdb.

  2. On the Tools menu, click Options, and in the Options dialog box, click the View tab.

  3. Under Show, click the System Objects check box, and then click OK.

  4. In the Database window, click the Tables tab. Using the right mouse button (right-click), click one of the system tables (those preceded with "MSys"), and then click Properties on the menu that appears. Note that the Replicable check box (or Replicated check box in Microsoft Access 7.0) is not available.

REFERENCES

"Building Applications with Microsoft Access 97", Chapter 20, "Using Replication in Your Application," page 557

Keywords : GnlApp kbusage
Version : 7.0
Platform : WINDOWS
Hardware : X86
Issue type : kbinfo

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.