PatThePostie
New member
- Local time
- Today, 04:19
- Joined
- Jul 14, 2017
- Messages
- 4
I'm having an issue whereby I set-up and configure an import of an Excel spreadsheet into Access 2016. I carefully configure which fields I want to have as an index and which fields should be skipped, and then opt to save the import for future use. The import on its first run is successful and the resulting table has the required fields only and the correct indexes. All well and good.
However, after running the saved import on the same spreadsheet any number of subsequent times, Access takes it upon itself to decide what fields it wants to index, and not respect the fields I previously told it to index. After dumping-out and examining the XML config for the saved import, all my config seems to be correct, Access is just not respecting it. This is causing me issues as Access decides to index fields I have not it not to import, and so the subsequent saved import run fails with the error "Cannot delete a field that is part of an index or is needed by the system". :banghead:
So far I have tried the following to rectify the problem, all to no avail:
Has anyone else experienced this? If so, is there any known work around or do I need to code my own Excel spreadsheet import in VBA?
However, after running the saved import on the same spreadsheet any number of subsequent times, Access takes it upon itself to decide what fields it wants to index, and not respect the fields I previously told it to index. After dumping-out and examining the XML config for the saved import, all my config seems to be correct, Access is just not respecting it. This is causing me issues as Access decides to index fields I have not it not to import, and so the subsequent saved import run fails with the error "Cannot delete a field that is part of an index or is needed by the system". :banghead:
So far I have tried the following to rectify the problem, all to no avail:
- Delete the destination table for the import before running the saved import.
- Delete the destination table for the import, perform a Compact and Repair, then try running the saved import.
- Create a new database and recreate the same import.
Has anyone else experienced this? If so, is there any known work around or do I need to code my own Excel spreadsheet import in VBA?