Share via

Error encountered in Access 2010 - Not reported elsewhere

Anonymous
2011-04-06T16:33:12+00:00

I have a spread sheet I was importing.  It is 8160 rows and A through FV columns.

During the load, all appeared to work well, until the end.  Then the following occurred:

Import Spreadsheet Wizard

Method "ExecuteTempImexSpec" of object '_WizHook' failed.

Also, after opening the table created within the data base a multitude of rows was flagged as: Row Truncation.

Does anyone have knowledge of this error; and what type of fix steps/workaround steps may help?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2011-04-06T17:14:44+00:00

So that's 238 columns? A Table is limited to 256 columns so you're not quite to the limit, but it's quite possible that the wizard has some overhead. Another limit is that any single row is limited to 2000 characters, so if a lot of these fields are Text you may be exceeding that limit.

If that's not the case, try creating a new, empty table (perhaps by importing, design view only); linking to the spreadsheet; and Appending to the table. Or you may need to import the spreadsheet piecemeal into more than one table.

In any case I'd hope you'll be normalizing this into a proper relational database - 50 columns is enormously wide, and 238 is just plain wrong.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-08-10T13:57:28+00:00

    Here ar work I have MS Office Pro Plus 2010 ... Access Version 14.0.7166.5000 (32-bit)

    Ran into this error trying to export a very small amount of data ...

    • 4 columns and 453 records of simple data ...

        - Number (long int), Text (Field Size 50), Number (long int), Text (Field Size 1)

    It seems absurd that this hasn't been fixed.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-12-23T12:16:07+00:00

    All good with these explanations but, error trapping must be more precise and specify the problem(s). We engineers, don't always have time to search every reason why something fails, this is not convenient at all. This has to be fixed in the source (MS Dev teams).

    If you have direct communication with them, please discuss it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2016-05-11T16:58:50+00:00

    Now the thread is five years old - has anybody fixed or addressed this?

    Was this answer helpful?

    0 comments No comments
  4. ScottGem 68,830 Reputation points Volunteer Moderator
    2014-12-23T13:34:59+00:00

    This is a 4 year old thread!

    Was this answer helpful?

    0 comments No comments