D
Danyelle
Everyone,
I have the need to create a database that acts as a master database
containing command buttons to open a variety of other Access databases we
support. This master database will function as a card catalog of sorts and
will be used by 100+ employees.
How do I write the code such that users are not opening an instance of the
second database while keeping the 1st open in memory? The command button
will need to redirect them completely away from the master database and allow
them full function of the 2nd database opened.
Thoughts? I have considered CreateObject, Run, and/or Shell. None of these
methods however seem appropriate for my needs.
Thank You
I have the need to create a database that acts as a master database
containing command buttons to open a variety of other Access databases we
support. This master database will function as a card catalog of sorts and
will be used by 100+ employees.
How do I write the code such that users are not opening an instance of the
second database while keeping the 1st open in memory? The command button
will need to redirect them completely away from the master database and allow
them full function of the 2nd database opened.
Thoughts? I have considered CreateObject, Run, and/or Shell. None of these
methods however seem appropriate for my needs.
Thank You