J
Jack Leach
Hello and thanks for any insight...
I've always tried to avoid doing this, but increasingly, between my
management software (access), my development application (access) and various
other tools (access) that are in seperate dbs, I'm finding myself doing a lot
of closing this app before opening that app, running a quick utility, then
closing and switching back to the main app. And this is if I'm not working
on development at the office.
I'm not sure what actually goes on when you have two instances of access
open. I *think* that these are the DBEngine(0).(0) workgroups? So an
additional instance would be DBEngine(0).(1)? Not sure...
I've always written code based on only having one instance open, for fear or
corruption or just plain unexpectedness... in fact I was just looking at an
API solution at mvps.org to make sure that there's no other instances open
before commiting to launch my main app startup.
Is it safe to keep more than one instance open at a time? Is there any easy
way to assure that all will work well? Does access have a tendancy to get
easily confusing (being that I don't tend to disambiguate.. e.i. its all
CurrentDb unless I have specific reason to specify a seperate db in a portion
of code).
I'm just curious if I can keep my current version of the usable app open
while I launch a seperate db to run a few quick utils, and maybe even be able
to work on the devel without having to keep closing all this out. And, I've
been curious about this besides for quite some time.
Thanks for any pointers.
--
Jack Leach
www.tristatemachine.com
"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
I've always tried to avoid doing this, but increasingly, between my
management software (access), my development application (access) and various
other tools (access) that are in seperate dbs, I'm finding myself doing a lot
of closing this app before opening that app, running a quick utility, then
closing and switching back to the main app. And this is if I'm not working
on development at the office.
I'm not sure what actually goes on when you have two instances of access
open. I *think* that these are the DBEngine(0).(0) workgroups? So an
additional instance would be DBEngine(0).(1)? Not sure...
I've always written code based on only having one instance open, for fear or
corruption or just plain unexpectedness... in fact I was just looking at an
API solution at mvps.org to make sure that there's no other instances open
before commiting to launch my main app startup.
Is it safe to keep more than one instance open at a time? Is there any easy
way to assure that all will work well? Does access have a tendancy to get
easily confusing (being that I don't tend to disambiguate.. e.i. its all
CurrentDb unless I have specific reason to specify a seperate db in a portion
of code).
I'm just curious if I can keep my current version of the usable app open
while I launch a seperate db to run a few quick utils, and maybe even be able
to work on the devel without having to keep closing all this out. And, I've
been curious about this besides for quite some time.
Thanks for any pointers.
--
Jack Leach
www.tristatemachine.com
"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)