Results 1 to 9 of 9
  1. #1
    Join Date
    Jul 2004
    Posts
    7

    Unanswered: Corrupted Import

    I've got a problem with access. When I try to import a excel file into it, the information I see in the import wizard is totally different from the information in the actual excel file. I can solve the import problem by setting a print area in excel first and importing it but I need to find the real cause as I'll need to automate the process. Anyone has any idea what is the cause? Thanks in advance.

    Michael

  2. #2
    Join Date
    Oct 2003
    Location
    Ger
    Posts
    1,969
    Provided Answers: 1
    Did you try to do it via VB?

  3. #3
    Join Date
    Oct 2003
    Location
    Ger
    Posts
    1,969
    Provided Answers: 1

    Lightbulb

    I mean using
    DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel97, Table2ImportYourData, "C:\yourExleFile.xls", True

  4. #4
    Join Date
    Jan 2004
    Location
    The Netherlands
    Posts
    421
    Hidden rows and columns
    Merged cells
    Invisible cells (text color = same as background)

    These usually are dead giveaways for strange things happening.

    Greetz

  5. #5
    Join Date
    Jul 2004
    Posts
    7
    Quote Originally Posted by hammbakka
    Did you try to do it via VB?
    Yup, imported using vb code but same thing still happens.

  6. #6
    Join Date
    Jul 2004
    Posts
    7
    Quote Originally Posted by namliam
    Hidden rows and columns
    Merged cells
    Invisible cells (text color = same as background)

    These usually are dead giveaways for strange things happening.

    Greetz
    Ok, I'll check the excel file in in office on Monday. Thanks for the help guys.

  7. #7
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    also consider saving to .CSV and importing the .CSV instead of .XLS
    ...gives you more control.

    izy
    currently using SS 2008R2

  8. #8
    Join Date
    Jul 2004
    Posts
    7
    Greetz, I was able to import successfully after removing a merged cell. But when I tried it again sometime afterwards, the same thing happened. Any idea why?

  9. #9
    Join Date
    Jul 2004
    Posts
    7
    Guys, I got another question. Can Access handle records of 30-40k? I ran a select,edit and update macro that I created on the tables and my Access keep crashing. Is it too much for Access to handle? I'm using Access 97.

Posting Permissions

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