I open the client database (Access 2003).
Navigate through a couple of VBA-enhanced forms.
Get to a certain form and click on a certain button.
The code breaks part way through event handling. The line it stops at, for what it is worth, says:
It stops exactly as if there were a breakpoint. But there is no breakpoint. (I did however run "clear all breakpoints".)
There is no error message. No err object has been raised. I press F5 and the code runs as normal.
If I close these forms and perform the same actions again, there is no halt and no problem. The break only occurs when that code is being invoked for the first time since the database was opened.
The same issue happens on other client workstations.
YOUR THOUGHTS? This is minor-yet-intolerable. We're in pre-launch testing and having the VB Editor pop up is not going to help anyone's comfort level!
[purple]_______________________________
Never confuse movement with action -- E. Hemingway [/purple]
Navigate through a couple of VBA-enhanced forms.
Get to a certain form and click on a certain button.
The code breaks part way through event handling. The line it stops at, for what it is worth, says:
Code:
If OpenArgs = "f_pProjectDetail--ADD" ThenIt stops exactly as if there were a breakpoint. But there is no breakpoint. (I did however run "clear all breakpoints".)
There is no error message. No err object has been raised. I press F5 and the code runs as normal.
If I close these forms and perform the same actions again, there is no halt and no problem. The break only occurs when that code is being invoked for the first time since the database was opened.
The same issue happens on other client workstations.
YOUR THOUGHTS? This is minor-yet-intolerable. We're in pre-launch testing and having the VB Editor pop up is not going to help anyone's comfort level!
[purple]_______________________________
Never confuse movement with action -- E. Hemingway [/purple]
