The way TransferDatabase is used in the example creates a new table in the MDB, so it wouldn't be a pre-existing key problem. But you have a point there, it might have something to do with duplicate records since Deleted=Yes brings in deleted records.

Stephen, have you tried Deleted=No?

>Stephen --
>
>I really haven't worked much at all in this area. It sounds like it could be a data-dependant error, hence the following question.
>
>Do you have a PK defined on the Access table to which you are importing data and is it possible that the table you're importing has duplicate key values (including the deleted records)?
>
> Jay
>
>>In a Microsoft Access Database Application (Access 2000) I am importing databases from a Visual FoxPro Application using VFP ODBC Driver Version 6.____
>>
>>I often get the following error:
>>
>>

>>[Visual FoxPro][ODBC Error] 0
>>

>>
>>The import fails. In most case a pack and reindex of the FoxPro Databases fixes this issue, however there is the occaision that it does not. In test cases, deleting the offending record fixes the problem, but as you can imagine, this is not a viable solution in a production level database.
>>
>>Any hints on error trapping for possible data errors would be helpful. or even better would be some sample code (if applicable) to scan data for possible conversion problems before import/export.
>>
>>Attached is the routine used to import the data for reference if needed:
>>
>>

>>
>>        DoCmd.TransferDatabase _
>>            acImport, _
>>            "ODBC Database", _
>>            "ODBC;DSN=dsnName;UID=", _
>>            acTable, _
>>            "tblName, _
>>            "tblName, _
>>            False
>>
>>NOTE: ODBC Settings Exclusive=No, NULL=Yes, Deleted=Yes
>>

>>
>>Thank You,