Re: Import Errors Table, unparsable record

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Liz (Liz_at_discussions.microsoft.com)
Date: 07/22/04 

Date: Thu, 22 Jul 2004 13:49:04 -0700

Hi John,

Thanks so much! It looks like it is, in fact, the character limit that is causing these errors. I am going to try switching these longer text fields to memo fields. But I was wondering, will this affect future imports into this table? That is, will text columns from Excel (or a text file) be imported into Access memo fields in the same way they would into Access text fields? I guess it is just not clear to me whether memo fields are stored differently to allow for the much greater capacity.

Thanks again,
Liz

"John Nurick" wrote:

> Hi Liz,
>
> Access does have a limit of approximately 2000 characters or 4000 bytes
> per record, excluding the contents of memo and OLE fields, and a wide
> Excel table can easily exceed this.
>
> (You can circumvent it either by creating the Access table manually,
> using memo fields for the wider Excel columns of text, or by linking to
> the spreadsheet and using queries to move the data into two or more
> narrower tables).
>
> Otherwise, the cause is almost certainly something to do with the data
> in your worksheet. There's some infromation here about how to interpret
> the Import errors table
> http://office.microsoft.com/assistance/preview.aspx?AssetID=HP051885461033&CTT=4&Origin=CH063648351033
>
>
> Also, the import routine often has trouble with hidden columns, and
> sometimes with cells that contain formulas. Make sure there are no
> hidden columns, and if there are formulas try getting rid of them by
> selecting the entire table and doing Copy and then Edit|Paste Special
> and selecting Values.
>
>
>
>
>
>
>
> On Wed, 21 Jul 2004 17:00:03 -0700, Liz <Liz@discussions.microsoft.com>
> wrote:
>
> >When importing an Excel spreadsheet into Access (both programs
> are the versions that came with XP Professional), the import was
> partially successful, but an "Import Errors Table" was generated due to
> many "Unparsable Records". In MS Access Help, it says this is often due
> to Text Delimiters, such as double quotation marks. But there were no
> such delimiters in the identified error locations. The errors were in
> many of the same fields for almost all rows, beginning with row 1.
> Another post suggested this may be due to character limits per record.
> Are there such limits in Access XP? Or could this be happening for
> another reason?
>
> --
> John Nurick [Microsoft Access MVP]
>
> Please respond in the newgroup and not by email.
>

Relevant Pages

  • RE: Memos or Comments in Excel
    ... Excel doesn't have a specific Memo type. ... A cell can be set to type "Text" ...
    (microsoft.public.excel.misc)
  • Re: ADODB is unable to copy more than 255 chars in excel cell
    ... > In the connection string you can set the extended property ... > That's the only way ADO/JET can READ excel cells beyond the 255 chars. ... The trick is to type the Excel table as MEMO e.g. ... convert values between data types but provides no effective mapping ...
    (microsoft.public.excel.programming)
  • Memos or Comments in Excel
    ... an Excel spreadsheet is easily accessible in Office Live. ... Does Excel support anything like an Accees Memo field where the ...
    (microsoft.public.excel.misc)
  • Re: Set Find to look in Values instead of Formulas by default?
    ... I think you can make it automatically set Find (on the menu bar) to look in Values using this Worksheet_Open event code... ... Private Sub Workbook_Open ... Rick (MVP - Excel) ... I have lots of data in hidden columns that I don't ...
    (microsoft.public.excel.programming)
  • Re: Exporting XLS into DBF3
    ... Rush, The Open Office tip is a good one, I'll have to try that out. ... Exporting "memo" size fields from Excel to VFP has been a pet peeve of mine ...
    (microsoft.public.fox.programmer.exchange)