Why is it calling this Excel file not an Excel file?

[Lou_Reed]

In the three zipped files that are attached one is an Access db, and the other two are Excel files.

I tried to import text.xlsm and it imports with no problem. The other one Production Tracker - Final Test.xlsm
does not.

It gives an error that it is not an Excel file when it clearly is.



I put in the error checking code on this Import/Export db. What is going on? Why is flagging "Production Tracker Final Test.xlsm"

as not an Excel file?

It is.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[John_G]

Lou - I told you this yesterday. When you get an error you cannot explain, turn error handling off, so you can see what and where the run-time error is.

If you do that here, you will see that the problem is not that the file is not an Excel file - it is -, but something else. I'm going to let you try to find it.

[Lou_Reed]

Okay, here is a link that claims to have solutions for the

Run-time error '32605:'

https://www.solvusoft.com/en/errors/...ields-columns/

I thought that just removing "empty" columns at the end of the spreadsheet would do it. I am not sure what is the reason behind the different solutions that they are taking about.

Please explain.

Respectfully,

Lou Reed

[Lou_Reed]

I thought the error was run-time error 32605. Access will not import more than 255 columns (fields) my Excel spreadsheet had far less than that with, but if you count the possibility that there are some columns with ghost
numbers or entries then removing a bunch of columns - say 20 at the end of the spreadsheet should do it.

It did not.

Now I really confused as to what can be causing this error.


Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[John_G]

The research I did on the errors I encountered indicated that there was probably corruption in the Access database. I created a new database, and imported all your database objects into it, and that did the trick. However, the Excel file needed some fixes - Access did not like the leading blanks in the column headers (Row 1), so I took them out with a new Excel macro RemoveLeadingBlanks.

The new database and the fixed up Excel file are attached.

[Lou_Reed]

Okay, thanks so much for your time and trouble.

By the way I have been working with computers for a long time. I still do not know what corruption is. It seems a catchall term for
when a file is just foobar.

Could this be the reason why Excel is calling the file not an Excel file. It sure looked like one when I open it up. But it did not import to Access. So maybe
that was hint that something is wrong.

Respectfully,

Lou Reed

[John_G]

It seems a catchall term for when a file is just foobar.

More or less. The structure of these file is so complex that all it takes is one small internal item (a pointer, for example) to be assigned wrong and the whole file is messed up.

Could this be the reason why Excel is calling the file not an Excel file.

No. Your error handling code produced that message regardless of what the runtime error was - it did not distinguish between different types of errors. An error handler can always display the actual error though, by using err.description. "err" is the error object in MS Access.