I have been using access for years but only recently have I been getting more serious and as a result I have been playing around with the different options / settings access offers.
It seems to me I have changed some setting because the set up of my error messages has drastically changed.
I used to get the standard error messages that has the options of "end" "debug"...
As of a few days ago my error messages have all changed to a different format. (I have uploaded an example of one of my error messages.)
I know the look of the error message would at first sight indicate a corrupt database but I have checked and rechecked and then rechecked again for corruption. I have followed guides by Allen Browne ( (such as this one - http://www.allenbrowne .com/recover.html) and a few others i was able to find on the web.
Another reason why I don't believe this isn't corruption is because I can fix the error and make the error message go away If i can find the line of code that is causing the problem. The formatting of the error message however makes it extremely difficult because it doesn't allow me to jump to the line of code in question.
In my current project I am using Error Handling but it does not catch the errors and instead displays them using that not very helpful error messsage.
Any thoughts or ideas on how to resolve this issue?
Any help would be greatly appreciated!
(btw I am using ms access 2003)
It seems to me I have changed some setting because the set up of my error messages has drastically changed.
I used to get the standard error messages that has the options of "end" "debug"...
As of a few days ago my error messages have all changed to a different format. (I have uploaded an example of one of my error messages.)
I know the look of the error message would at first sight indicate a corrupt database but I have checked and rechecked and then rechecked again for corruption. I have followed guides by Allen Browne ( (such as this one - http://www.allenbrowne .com/recover.html) and a few others i was able to find on the web.
Another reason why I don't believe this isn't corruption is because I can fix the error and make the error message go away If i can find the line of code that is causing the problem. The formatting of the error message however makes it extremely difficult because it doesn't allow me to jump to the line of code in question.
In my current project I am using Error Handling but it does not catch the errors and instead displays them using that not very helpful error messsage.
Any thoughts or ideas on how to resolve this issue?
Any help would be greatly appreciated!
(btw I am using ms access 2003)
Comment