This has me stumped. I have an Access 97 database that runs fine on everthing I have except Windows XP Pro.
It seems that when the code (click event) hits a message box
it creates the message box on the screen but then causes a different application to become active or gives the wrong form the focus. The line of code is below. Num is not declared in the function but is set to a function that returns a long integer... I'll post if fixing the declaration works (I hate maintaining other's work).
MsgBox NUM & " RECORD(S) HAVE BEEN UPDATED"
It seems that when the code (click event) hits a message box
it creates the message box on the screen but then causes a different application to become active or gives the wrong form the focus. The line of code is below. Num is not declared in the function but is set to a function that returns a long integer... I'll post if fixing the declaration works (I hate maintaining other's work).
MsgBox NUM & " RECORD(S) HAVE BEEN UPDATED"
