Workspace in Access 2002

  • Thread starter Thread starter ray
  • Start date Start date
R

ray

Hello All:

If I launch two instaces of Access, is this considered two
seperate workspaces. I'm trying to improve my programing
skills by understanding the DBEngine object model
completely.

Thanks,
Ray
 
If I launch two instaces of Access, is this considered two
seperate workspaces. I'm trying to improve my programing
skills by understanding the DBEngine object model
completely.
Click to expand...

debug.print DBEngine.Workspaces.Count


Tim F
 
Tim,

I open two instances of Access and inserted the code you
provided below. The workspace count was 1. I assume that
unless I explicitly create/open another database within a
workspace, all instances of access are contained in the
same default workspace. Am I correct?

Ray
 
If I launch two instaces of Access, is this considered two
seperate workspaces. I'm trying to improve my programing
skills by understanding the DBEngine object model
completely.
Click to expand...


It's not really a matter of how they're "considered".

A single instance of Access can have any number of Workspaces. (See the
CreateWorkspace method.)

Two different instances of Access are, by definition, different.

It follows that the Workspace(s) of one instance of Access are, by
definition, different to the Workspace(s) of any other instance of Access.

HTH,
TC
 
David, DAO does various things that ADO doesn't - for example, programattic
security manipulation. It really is not accurate to say that DAO is
"obsolete".

TC
 
TC said:
I'm sure they want you to use ADO instead.
Click to expand...

If MS wanted us to use ADO, then surely they would have made it work. There
are simply too many things that are not available, and for working with Jet
databases it's a fool's option. It also seems to me to be logically
corrupt: being able to "open" an INSERT query, or execute a "SELECT" feels
like it was designed by the web team rather than anyone who knows about
database functions.

Still, what do I know?

All the best



Tim F
 
1) MS is still (or again) writing KB articles advising you to
use DAO for certain classes of applications.

2) DAO only supports the 'backwards compatible' Jet 2/Jet 3
version of SQL: the 'forwards compatible' syntax supported
by ADO and Jet 4 is switched off when you use DAO.

Yes, DAO is best: No, it's not depreciated (as much). No, I
would not advise anyone to <learn> DAO until they had already
learned ADO. Sometimes, being the best technology is not
enough.

(david)
 
Ray,

First, to answer your question, each instance of Access is
its own DBEngine.

Second, you should be concentrating on ADO and its
Connection object model, which obeys the same rules with
regard to each instance of Access.

DAO is deprecated and probably won't appear in future
versions of Access. For sure, no new development is being
done on it.

David Gray
P6 Consulting
http://www.p6c.com/
 
Back
Top