Anakardian
Registered User.
- Local time
- Today, 01:21
- Joined
- Mar 14, 2010
- Messages
- 173
I recently experienced a puzzling problem with DoCmd.TransferSpreadsheet.
After having the some code run successfully for several months on a daily basis, the data from a spreadsheet was suddenly not imported anymore.
There were no error messages or any hint of why the import failed.
After trying a great deal of things I could finally get it to trigger an error.
It turned out that someone had written something in a new column and then deleted it.
Since it had once contained something the Docmd.TransferSpreadsheet tried to import the extra column. As there was no space for it in the database, the import failed without errors.
Once the empty additional column had been deleted the import once again went smoothly.
The way I discovered the problem was by doing an import through the import wizard. When it ran I received and error that the field "f6" did not exist in the destination table.
After having the some code run successfully for several months on a daily basis, the data from a spreadsheet was suddenly not imported anymore.
There were no error messages or any hint of why the import failed.
After trying a great deal of things I could finally get it to trigger an error.
It turned out that someone had written something in a new column and then deleted it.
Since it had once contained something the Docmd.TransferSpreadsheet tried to import the extra column. As there was no space for it in the database, the import failed without errors.
Once the empty additional column had been deleted the import once again went smoothly.
The way I discovered the problem was by doing an import through the import wizard. When it ran I received and error that the field "f6" did not exist in the destination table.
