如何在C# WPF中无需DoCmd创建Access97数据库间链接表？

Great question—you absolutely can create linked tables between Access 97 databases without relying on DoCmd, and this will avoid the silent crashes you're dealing with. The issue with DoCmd is almost certainly related to Access Interop dependencies or runtime environment quirks on client PCs. Let's break down two reliable approaches:

Method 1: Use DAO (Recommended for Access 97) #

DAO (Data Access Objects) is the native data framework for older Access versions like 97, so it's the most stable choice here. Here's how to implement it in your C# WPF app:

1. Add a DAO Reference:

   • Right-click your project in Visual Studio → Add → Reference → COM → Find and select Microsoft DAO 3.6 Object Library (this is fully compatible with Access 97).

2. C# Code to Create the Linked Table:

   using DAO;
   
   public void CreateAccess97LinkedTable(string targetDbPath, string linkedDbPath, string sourceTableName, string linkedTableName = null)
   {
       // Default to the source table name if no linked name is provided
       linkedTableName ??= sourceTableName;
   
       using (var dbEngine = new DBEngine())
       {
           // Open the target Access 97 database (read/write, no exclusive lock)
           var targetDb = dbEngine.OpenDatabase(targetDbPath, false, false, "");
   
           try
           {
               // Build the connection string pointing to the other Access database
               var connectString = $"MS Access;PWD=;DATABASE={linkedDbPath}";
               // Add a password to the string if your database uses one: PWD=yourPassword;
   
               // Create a TableDef object to define the linked table
               var tableDef = targetDb.CreateTableDef(linkedTableName);
               tableDef.Connect = connectString;
               tableDef.SourceTableName = sourceTableName;
   
               // Append the TableDef to the target database to finalize the link
               targetDb.TableDefs.Append(tableDef);
           }
           catch (Exception ex)
           {
               // Make sure to log or handle exceptions—silent crashes are often unhandled errors
               Console.WriteLine($"Failed to create linked table: {ex.Message}");
               throw; // Re-throw if you want to handle it upstream
           }
           finally
           {
               targetDb.Close(); // Always clean up database connections
           }
       }
   }
   

   Key Notes: #

   • Ensure both the target and linked databases are closed before running this code—Access locks databases exclusively when open.
   • If your databases are password-protected, update the connectString to include the password.

Method 2: Use ADO with SQL DDL #

If you prefer using ADO instead, you can execute a SQL CREATE TABLE statement to create the linked table. This works for Access 97, though DAO is generally more reliable for this specific task:

using System.Data.OleDb;

public void CreateLinkedTableWithADO(string targetDbPath, string linkedDbPath, string sourceTableName, string linkedTableName = null)
{
    linkedTableName ??= sourceTableName;

    // Connection string for Access 97 (uses Jet 4.0 provider)
    var connString = $"Provider=Microsoft.Jet.OLEDB.4.0;Data Source={targetDbPath};";

    using (var conn = new OleDbConnection(connString))
    {
        conn.Open();

        // SQL DDL to create the linked table—note the dummy column is required for syntax
        var sql = $@"CREATE TABLE [{linkedTableName}] 
                      (DummyColumn TEXT) 
                      WITH OWNERACCESS OPTION
                      IN '' [MS Access;DATABASE={linkedDbPath}];";

        using (var cmd = new OleDbCommand(sql, conn))
        {
            try
            {
                cmd.ExecuteNonQuery();
            }
            catch (Exception ex)
            {
                Console.WriteLine($"ADO linked table error: {ex.Message}");
                throw;
            }
        }
    }
}

Why This Fixes the Crash #

Both DAO and ADO interact directly with the Access Jet engine without relying on the Access UI or DoCmd. This eliminates the interop-related instability you're seeing—you don't even need the full Access application installed on client PCs, just the Jet/DAO/ADO components (which are pre-installed on most Windows systems).

Quick Troubleshooting Tips #

• Check Jet Engine: Ensure client PCs have the Microsoft Jet 4.0 Engine installed (critical for Access 97 compatibility).
• File Permissions: Make sure your app has read/write access to both database files—permission issues can cause silent failures.
• Log Everything: Wrap all database operations in try/catch blocks and log exceptions. The "no event log" issue is likely because the exception wasn't being caught or logged.

内容的提问来源于stack exchange，提问作者Rob Bowman