I have several Access 2013 databases into which I import Excel data to process (and subsequently export) - all manually (no macros).
One day (yesterday) - this process stopped working.
I select the Excel icon from the "Import and Link" ribbon. The "Get External Data - Excel Spreadsheet" window opens. I choose the file I want by selecting "Browse". I can select either import, append or link - regardless I get the same error when I click "OK".
The error consists of a "Type Mismatch" Error pop-up window. When I click OK in that, I get an incompletely formed window with "mx_FrmMain" in the title bar, a white field across the top, a blank field in the middle with vertical and horizontal slide bars, a gray field at the bottom and 4 buttons "Cancel" "<Back" (which is greyed out), "Next>" and "Finish".
Clicking "Next" results in "The expression you entered refers to an object that is closed or doesn't exist" (which makes sense since no data was imported, no table was created).
It doesn't matter whether I attempt to import files that used to work in the past or a simple and small data set (3 rows, "a", "b", "c" as the column headers and 1, 2, 3, 4, 5, 6 spread across 3 columns and 2 rows). I get the same error. The error doesn't happen if I import into a blank database. But, once my database has content in it (whether just a table or tables and queries), the error occurs all the time.
I have uninstalled and reinstalled all of Office 2013. Immediately upon re-install - it seemed to work (that is, the "type mismatch" error message didn't occur, but something wasn't right with the data. (It appeared that "0" (zero) values were being imported incorrectly - I ran out of time to debug. When I came in this morning, when I started Office, I got a "configuration in process" message (that I didn't get yesterday). After that, I was back to where I started yesterday - no import - Type Mismatch Error.
As this used to work "last week", I know that all the data types and formats are consistent between what is in Excel and what is in Access. This used to work - until this week. I've changed nothing in either the formatting or content of the source Excel file or the Access database.
I don't think it is a data type/format problem. Something about how Access is processing incoming data when there is already content in the database is new.
I am using Windows 7 Enterprise - Version 6.1 (build 7601: Service Pack 1)
Microsoft Office Professional Plus 2013 - Version 15.0.4859.1000 32-bit