when using a command button to close a form, i have seen both:
... DoCmd.Close
and
... DoCmd.Close acForm, Me.Name
? is there an advantage / reason for... one over the other?
as always, with appreciation in advance,
m.
DoCmd.Close
Competent Performer
Windows 10 
Access 2013 64bit
when using a command button to close a form, i have seen both:
... DoCmd.Close
and
... DoCmd.Close acForm, Me.Name
? is there an advantage / reason for... one over the other?
as always, with appreciation in advance,
m.
Virtually Inert Person
Windows 10 Access 2016
Without specifying an object you might close the active object which can cause an unexpected result - what you expect to be the active object might not be. Can also be problematic when trouble shooting code as the code window may be active. IMO, best to be explicit and avoid surprises.
EDIT - I realize that often when code behind a form is executing, that form is likely the active object. However, sometimes such calls are passed to public subs or functions, and sometimes code can branch off and make some other object the active object (e.g. you want to get the Text property from another form so you have to set focus to that control, which by default, makes some other form the active object). As long as you understand the implications, you should be fine. I'm just saying in my initial post that you can't go wrong by being explicit about it.
Last edited by Micron; 02-13-2021 at 11:59 AM. Reason: spelin and gramur
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Competent Performer
Windows 10 Access 2013 64bit
perfect... thnx!
Virtually Inert Person
Windows 10 Access 2016
You probably didn't see my edit, so here's a followup to trigger an email.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Posting Permissions
Reply With Quote