J
JimBurke via AccessMonster.com
I have two Access applications that I support. In both of them I have an On
Activate event defined for my main form. On my test machine (my laptop) if I
have that form displayed and then go to another window within Windows, then
go back to my Access app's form again, the On Activate event gets fired. On
our production server, the event is not firing when this happens. Any ideas
why? The odd thing is this only happens with one of the applications - with
the other one the event fires on the server! Any help is appreciated. Just to
let you know what I'm doing, in both apps my main form displays patient
information. I need to keep track of who the current patient is because when
the form is left (either because of opening other forms or going to different
windows) and then it is returned to it won't go back to that same patient
unless I keep track of the 'old' patient ID and go back to it in the activate
event. By the way, I put a break point at the first line of the Activate
event to test whether it is going there or not, and in the appl that behaves
'properly' the breakpoint is hit, in the other one it is not (and I know that
breakpoints in general do work on the server).
I guess the real question would be is there any way to prevent this behavior,
i.e. is there a parameter somewhere that tells Access to stay at the current
record when the user leaves the main form (from opening other forms or
changing windows) and then ends up back at the main form again? Pretty sure
that is a No, but maybe not. That would be the ideal solution.
Activate event defined for my main form. On my test machine (my laptop) if I
have that form displayed and then go to another window within Windows, then
go back to my Access app's form again, the On Activate event gets fired. On
our production server, the event is not firing when this happens. Any ideas
why? The odd thing is this only happens with one of the applications - with
the other one the event fires on the server! Any help is appreciated. Just to
let you know what I'm doing, in both apps my main form displays patient
information. I need to keep track of who the current patient is because when
the form is left (either because of opening other forms or going to different
windows) and then it is returned to it won't go back to that same patient
unless I keep track of the 'old' patient ID and go back to it in the activate
event. By the way, I put a break point at the first line of the Activate
event to test whether it is going there or not, and in the appl that behaves
'properly' the breakpoint is hit, in the other one it is not (and I know that
breakpoints in general do work on the server).
I guess the real question would be is there any way to prevent this behavior,
i.e. is there a parameter somewhere that tells Access to stay at the current
record when the user leaves the main form (from opening other forms or
changing windows) and then ends up back at the main form again? Pretty sure
that is a No, but maybe not. That would be the ideal solution.