ACC2: Import Errors Table Lists Incorrect Row Numbers

Last reviewed: May 30, 1997
Article ID: Q148466
The information in this article applies to:
  • Microsoft Access version 2.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you import a spreadsheet that causes a "key violation" error, the resulting Import Errors table lists row numbers one greater than the actual spreadsheet row. For example, if row 2 from the spreadsheet file causes a key violation, then it is listed in the Import Errors table as row 3 (not row 2).

RESOLUTION

You can manually subtract 1 from the row numbers listed for "key violation" errors in the Import Errors table.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open the sample database NWIND.MDB.

  2. Export the Shippers table to a Microsoft Excel 5.0 file called Shippers.xls.

  3. Import the Shippers.xls file and append the data to the Shippers table.

  4. Click OK when you receive the following error message:

          Import to Shippers finished - 4 records processed. 4 errors
          occurred. Error descriptions with associated row numbers of bad
          records can be found in Microsoft Access table
          Import Errors-<name>.
    

  5. Open the Import Errors table. Note that the row numbers for key violations are 1 greater than the actual spreadsheet row.

REFERENCES

For more information about the Import Errors table, search for "import errors," and then "import errors table" using the Microsoft Access Help menu.


Keywords : IsmProb kb3rdparty
Version : 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


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