Hi All,
I have a complex text reader that uses the File System Object (Access03). There is a custom error tracking system that pinpoints errors with messages that help track down errors.
An error came up that stopped execution with no messages. By tracking down the line of code that caused the error and running it in the immediate window it turned out to be a windows error when the FSO was moving a file.
I would like to trap windows errors and display them so that users can address these problems themselves. Does anyone know how to trap windows errors and store them for later use.
Thanks,
alr
_____________________________________
There is no rule more invariable than that we are paid for our suspicions by finding out what we expected.
Henry David Thoreau
I have a complex text reader that uses the File System Object (Access03). There is a custom error tracking system that pinpoints errors with messages that help track down errors.
An error came up that stopped execution with no messages. By tracking down the line of code that caused the error and running it in the immediate window it turned out to be a windows error when the FSO was moving a file.
I would like to trap windows errors and display them so that users can address these problems themselves. Does anyone know how to trap windows errors and store them for later use.
Thanks,
alr
_____________________________________
There is no rule more invariable than that we are paid for our suspicions by finding out what we expected.
Henry David Thoreau
