|
-
Jan 12th, 2013, 04:59 PM
#3
Thread Starter
PowerPoster
Re: How Does VB I Want to Use MSAccess
Thanks for input.
Logically (if I can rely on my logic??)
It makes since that if the OS on my machine defines *.mdb as being used by an Access database that somewhere there is information stored and accessible that
anything with *.mdb is an Access mdb.
As you point out, it further makes sense that since I am referencing Microsoft DAO 3.51 object library (Instead of Java DAO or Oracle DAO) that somewhere within
DAO it must reference (default to) Jet databases -- however MS defines them (e.g. is Access, MySQL, or SQL Server all considered Jet)?
I found this on Wikipedia:
There are three modules to Jet: One is the Native Jet ISAM Driver, a dynamic link library (DLL) that can directly manipulate Microsoft Access database files (MDB) using Indexed Sequential Access Method (ISAM). Another one of the modules contains the ISAM Drivers, DLLs that allow access to a variety of ISAM databases, among them Xbase, Paradox, Btrieve and FoxPro, depending on the version of Jet. The final module is the Data Access Objects (DAO) DLL. DAO provides an API that allows programmers to access JET databases using any programming language.
So logically then (??) if I am manipulating an *mdb file (really an ISAM file??) using DAO, I guess in affect that that file (*.mdb) is really being manipulated WITHOUT ever opening MSAccess
(which is really a separate program and GUI ??) .
So if the above is correct, why can't I open two different *.mdb files using DAO and then copy records between them (see Database forum >> http://www.vbforums.com/showthread.p...ss-Databases)?
Last edited by dw85745; Jan 12th, 2013 at 05:16 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|