You receive an "File sharing lock count exceeded" error message when you synchronize two replicas in Access 2000

The MaxLocksPerFile setting allows the Microsoft Jet database engine to complete large transactions without exceeding a specified record lock limit. Instead of exceeding this limit, the Jet database engine splits a transaction into two or more parts; after one part has been committed, the Jet database engine frees the locks so that they can be reused. As a result, fewer locks are required to complete the transaction. This prevents a Novell Netware server, which limits the maximum record locks per connection to 10000, from crashing when that value is exceeded.

However, the Jet database engine does not split the transaction when it synchronizes two replicas. If the transaction cannot be completed within the limit specified in the MaxLocksPerFile setting unless it is split into parts, you receive the error described in the "Symptoms" section, and the synchronization does not occur.

Steps to Reproduce Problem

WARNING: The following steps may require up to 400 MB of free disk space. The sample procedure fills a table with a large amount of data; running it may take a long time, during which your CPU is unavailable.

1. Start Microsoft Access and open a new blank database.
2. Create the following table:
   
   

   Field Name	Data Type	Field Size
   ID	Number	Long Integer
   Field1	Text	50
   Field2	Text	50
   Field3	Text	50
   Field4	Text	50

3. Save the table as tblTable1. When asked if you want to create a primary key, click No.
4. On the Tools menu, point to Replication, and click Create Replica. When prompted to close the database, click Yes. When prompted to make a backup, click No.
5. In the Location of New Replica dialog box, note the location and file name of the new replica. Click OK.
6. Click OK when prompted that the Design Master was successfully created.
7. Open a new, blank module.
8. On the Tools menu, click References.
9. Scroll down through the Available References and click to select the check box for the Microsoft DAO 3.6 Object Library. Then click OK.
10. Type the following procedure:

    Function Filler(lngNumRecs As Long)
        Dim lngLoopCount As Long
        Dim strFillerString As String
        Dim db As Database
        Dim rs As Recordset
    
        strFillerString = ""
    
        For lngLoopCount = 1 To 40
            strFillerString = strFillerString & "x"
        Next lngLoopCount
    
        Set db = CurrentDb
        Set rs = db.OpenRecordset("tblTable1")
    
        For lngLoopCount = 1 To lngNumRecs
            rs.AddNew
            rs![ID] = lngLoopCount
            rs![Field1] = strFillerString
            rs![Field2] = strFillerString
            rs![Field3] = strFillerString
            rs![Field4] = strFillerString
            rs.Update
        Next lngLoopCount
    
        db.Close
        MsgBox "Process Completed."
    End Function
    

11. Save the module as Module1. Type the following line in the Immediate window, and then press ENTER:

    ?Filler(500000)
    

    NOTE: This procedure may take a long time to run and may require as much as 400 MB of free disk space. After the process has completed, continue on to the next step.
12. On the Tools menu, point to Replication, and then click Synchronize Now.
13. In the Synchronize Database '<name>' dialog box, click OK.
14. Click Yes to close the database and begin synchronization.

A progress indicator with the message "Synchronizing Replicas" appears, but eventually you receive the error described in the "Symptoms" section.