Good afternoon Folks,
I'm hoping someone might be able to assist here. I have a database that I have created that imports fixed width text files on a daily basis, which are produced by a scanning system.
I have an import specification for the text files and code that uses that import specification which runs automatically each day one the import button is activated.
I have investigated my problem from an Access perspective and the problem is being generated there. The scanning software for some reason causes some sort of bug to appear in the text file which is very random as to where it appears.
Now what happens when the automated process is run in Access, if this bug is in the text file Access does not import the text file, however if I manually import the text file Access allows the file to be imported and generates an import error message identifying the offending row(s) in the text file and the message Type Converstion Error.
So the problem is getting access to still import the text file even if there is a converstion type error in the text file when it is running in automatic mode.
My idea is for the importErrors table still to be generated with the information Access generates when manually importing the text files so that I can still identify the offending rows and take action accordingly.
If anyone has any suggestions or pointers of examples of how this sort of problem can be dealt with I would be most grateful.
Regards
John
I'm hoping someone might be able to assist here. I have a database that I have created that imports fixed width text files on a daily basis, which are produced by a scanning system.
I have an import specification for the text files and code that uses that import specification which runs automatically each day one the import button is activated.
I have investigated my problem from an Access perspective and the problem is being generated there. The scanning software for some reason causes some sort of bug to appear in the text file which is very random as to where it appears.
Now what happens when the automated process is run in Access, if this bug is in the text file Access does not import the text file, however if I manually import the text file Access allows the file to be imported and generates an import error message identifying the offending row(s) in the text file and the message Type Converstion Error.
So the problem is getting access to still import the text file even if there is a converstion type error in the text file when it is running in automatic mode.
My idea is for the importErrors table still to be generated with the information Access generates when manually importing the text files so that I can still identify the offending rows and take action accordingly.
If anyone has any suggestions or pointers of examples of how this sort of problem can be dealt with I would be most grateful.
Regards
John
Last edited:
