BUG: Distribution Task Fails to Synchronize Access .MDB with Err

Last reviewed: May 14, 1997
Article ID: Q168522
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16831 (6.5)

SYMPTOMS

When replicating a table from SQL Server to a Microsoft Access .mdb file, the distribution task fails to transfer the data to the .mdb file. The task history of the distribution task contains the following error message:

   S1000[Microsoft][ODBC Microsoft Access 97 Driver]
   Reserved error (-3033); there is no message for this error.

CAUSE

A datetime column of the replicated table contains NULL in the first record(s) and values in the following record(s). This is misinterpreted by the distribution task.

WORKAROUND

To work around this problem, do either of the following:

  • Replicate with "No Data Synchronization", by performing the following steps:

    1. Import the table from the SQL Server into Microsoft Access.

    2. Rename the table to the desired or original name.

    3. Replicate the table to Microsoft Access with "No Data

          Synchronization".
    
  • Temporarily avoid using NULLs, by doing the following:

    1. Update the NULLs of the datetime column to some other value.

    2. Replicate the table to Microsoft Access.

    3. When the tables are synchronized, update the datetime column back to

          NULL.
    

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: replication jet odbc
Keywords : kbbug6.50 kbinterop SSrvRep
Technology : ODBC
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbworkaround


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: May 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.