detail form

[Guest]

I have a form that opens when a user selects a client that collects specific
information about the client. For performance reasons, the form is invisible
until invoked, then becomes visible. I see the options for populating that
form as 1) apply filter to the form with the selection criteria, 2)
programmatically change Recordsource of the form to the specific record, or
3) move to correct record with the .FindFirst function.

Is there a performance or any other advantage to any of these approaches? I
am thinking in terms of many users editing the data, all using this form. The
2nd option looks best in terms of not holding a lot of records on the
desktops that other users may be editing...

Appreciate any guidance.
Thanks

 

[Guest]

Options 1 and two both cause a requery of the recordset.
Option 3 is the usual way to do this.
Hopefully, you are using a split database and each user has their own copy
on their computer.

 

[Guest]

Thanks, Dave, this really helps. I have found in the past that when I guess,
I usually do things in a very non-standard way that tangles up later. I am
trying to do any new coding as "industry standard" as possible.