G
Guest
I have a form with a button that performs a file import using VBA code. When
first opening the application and clicking the "Import" button, the code
stops at a line of the procedure even though there is no break point. After
pressing F5, code proceeds as expected until completion. If we reopen the
form, the import behaves normally (no stopping in code). Several days later
if we repeat the opening of the form and execution of Import, the same
behavior occurs: First time: stops at line in code; additional times, normal
behavior.
The funny thing is that on two different computers, the code stops at
different lines with the line being repeatable on each computer. Computer #1
stops at a line that begins with "On Error". Computer #2 stops at a line
that begins with "Me.lblMessage.Caption = ". This behavior makes no sense to
me. Has anyone else experienced this behavior and have any ideas about
avoiding it. End user does not find this behavior funny.
first opening the application and clicking the "Import" button, the code
stops at a line of the procedure even though there is no break point. After
pressing F5, code proceeds as expected until completion. If we reopen the
form, the import behaves normally (no stopping in code). Several days later
if we repeat the opening of the form and execution of Import, the same
behavior occurs: First time: stops at line in code; additional times, normal
behavior.
The funny thing is that on two different computers, the code stops at
different lines with the line being repeatable on each computer. Computer #1
stops at a line that begins with "On Error". Computer #2 stops at a line
that begins with "Me.lblMessage.Caption = ". This behavior makes no sense to
me. Has anyone else experienced this behavior and have any ideas about
avoiding it. End user does not find this behavior funny.