This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have been importing Excel files for years. I recently upgraded to Access 2007 on a shared server (Windows Server 2003 R2, Service Pack 2) and now I can't import. Every time I get "Subscript out of Range" when I use the Import Wizard. The file is correct with the correct field names and data. I have tried importing into different tables and always get this error. I can try an .xls or an .xlsx file and neither work.
I have to paste the records in.
Help!
A family of Microsoft relational database management systems designed for ease of use.
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.
Wildcard Characters) that might confuse Access?
This was my problem. I had Serial# and # a few other places!
I sometimes experience this problem in Access 2007, too. Sometimes I am not able to import from Excel 2007 into an existing table. The existing table was created by a prior import process. I can import into a new table without any problem. However, if I have to do that every time, then that reduces the efficiency of the application. It seems like the table in Access somehow becomes corrupted, but I'm not sure why. It would be nice if Microsoft would make the error reporting more robust. Stating "subscript out of range" is like calling 911 and stating "there is an accident somewhere in the city".
Is there a question in there somewhere that I missed? Did you review the above? Does any of apply to you?
-- Gina Whipp 2010 Microsoft MVP (Access) Please post all replies to the forum where everyone can benefit.
I think that you post was directed at me so here is my reply. First of all, thank you for replying to my post. Secondly, I was following the original post because I sometimes encounter the same type of problem as ccento. I did not post a question since the original post seemed to focus on the same type of problem that I have encountered. Yes, I reviewed the entire thread prior to contributing to the thread. Although it seems to me that I have encountered the same problem or a similar problem as ccento, I don't know if the reason for the problem that I have encountered is the same as the reason for the problem that ccento has encountered. The problem has ceased for me. I'm not sure, but I think that my problem may have had something to do with either the data in my source (Excel file) or the labels for my column headings. I very carefully made sure that the labels for my column headings were acceptable to Access. Then I updated my data source file to use the exact same headings that I used in Access. Then I made sure that there were no empty columns to the right of my last legitimate column and no empty rows below my last legitimate row in my data source file. This seemed to fix the problem for me. Now I can quickly and easily import data from my Excel source file into my existing Access table without any difficulties.
Thanks for your help.
Plansforgood...
Thanks for the follow up and glad the problem for you is resolved...
--
Gina Whipp
2010 Microsoft MVP (Access)
Please post all replies to the forum where everyone can benefit.