Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Import Error - Unparsable record (Access 2003)

    What does the import error "Unparsable Record" mean when importing records into Access from a .CSV file?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Check whether there are text values in the problem record that contain the double quote character <code>"</code>. These must be doubled, otherwise Access gets confused. Example:
    <code>
    "3.5" disk"
    </code>
    will confuse Excel. To import, change it to
    <code>
    "3.5"" disk"
    </code>

  3. #3
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Yes there are plenty of double quotes in the text fields. Is there an easy way to change just the double quote characters in your example to ""? . A global find/replace will change all the quotes to double quotes (including the text qualifiers).

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    The best way to do that would be to replace the double quote characters in the source application before exporting to a .csv file. In the .csv file, it's difficult to do it automatically.

  5. #5
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Can you change the export process that produces these text files so that it puts the double quotes in?
    Regards
    John



  6. #6
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Unfortunately, no. The system from which I am exporting the records is a proprietary system and I cannot customise it in any way.

  7. #7
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    There are thousands!

  8. #8
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Sue the idiots who designed the faulty csv export! <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>

  9. #9
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    I have another idea.
    I could open the .CSV file and
    a) replace all delimiters "," with semi-colons; and
    [img]/forums/images/smilies/cool.gif[/img] replace all " with ""
    Then I can import this into Access. Will this work?

  10. #10
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    That depends - if some of the fields could contain "," you still have a problem. If not, you might be in luck.

  11. #11
    Lounger
    Join Date
    Aug 2006
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    I found another work around. By opening the .CSV file with Excel and saving it in columns, then importing it into Access, the quotes are all recognised and I don't get the import errors.

    When I import into Access directly from the .CSV file I am able to save the import / export specification. This saves me a lot of time because I will have to repeatedly import these records.

    However, when I open the .CSV file with Excel, it automatically assumes that each column is "General".

    Is there a way to save an import specification for Excel?

  12. #12
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    Excel doesn't have import specifications. However, you could change the extension to .txt, then record a macro of opening and saving the file. For .txt files, Excel will display the Import Text Wizard, letting you specify the type for each column. Afterwards, you can edit the recorded macro to work with a .csv file.

  13. #13
    Star Lounger
    Join Date
    Apr 2003
    Location
    Kansas City, Missouri
    Posts
    66
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    I just ran into this problem myself. I ran a search and found this topic.

    My problem is a bit different in that I don't have any double quotes. I just checked the records in question for any offending characters. I see some semicolons, but I have hundreds of semicolons that did not trigger the Unparsable Record error.

    Are there other characters I should keep an eye open for?

    Kevin

    PS: This is for Access 2003/ SP 2

  14. #14
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Import Error - Unparsable record (Access 2003)

    We'd have to know more about the data.

  15. #15
    Star Lounger
    Join Date
    Apr 2003
    Location
    Kansas City, Missouri
    Posts
    66
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Import Error - Unparsable record (Access 2003)

    The information is confidential so I can't attach it, but I can say that it contains only alphanumeric characters, commas, periods, apostrophes, semicolons, and parentheses. No unusual characters are visible.

    I accidentally solved my own problem. I had to address another error--the truncated record. Not all of the data were good with Text fields. I changed those to Memo fields. When I reimported the data, I received no errors.

    So, I guess I'm happy. I'd like to have known why it caused that error for some seemingly innocent text, but I may just attribute it to the Memo format being more robust than the Text format. Yeah, that'll be the reason.

    Hmm, I don't have any Chr(13) characters, but I suppose I could have had a Chr(10). Does a Memo field handle that better than a Text field?

    Kevin

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •