Re: Access vs SQL

How about if we say that an .mdb file is an Access file that wraps a JET
database and adds extensions of its own?

"Can't we all just get along?"

I think the fundamental point here is that there is no such thing as DATA
stored in Access format. An Access file is DATA stored in a JET database
along with Access elements such as reports, forms, VBA code, etc. and all of
that is placed in an Access .mdb file.

The proof in the pudding is that the data stored in an Access file can be
programmatically accessed and manipulated without having the Access client
because the actual data is not stored in an Access format, but in a JET
database.




"Paul Clement" <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx> wrote in message
news:t1il51du905tem6agf6esaea8mj06300d9@xxxxxxxxxx
> On 10 Apr 2005 18:58:31 -0700, aatcbbtccctc@xxxxxxxxx wrote:
>
> ¤ Not so, Cor.
> ¤
> ¤ MS Access does not contain any of the base technologies for creating &
> ¤ managing tables & indexes; parsing, optimizing & executing SQL; or any
> ¤ of the other things that database products have to do.
> ¤
> ¤ Those technologies all reside in a completely seperate product, MS Jet.
> ¤ Access uses the Jet API to create & maintain tables & indexes, execute
> ¤ SQL, and so on.
> ¤
>
> This is incorrect.
>
> I'm not sure why you're attempting to separate Jet from Microsoft Access.
> Each version of Microsoft
> Access is actually hard-wired for a specific version of Jet and the
> functionality is essentially
> integrated. You can also use DAO, ADO etc (independently) to work with an
> Access database directly
> or via OLEDB or ODBC drivers but there isn't the same level of support as
> when using the Microsoft
> Access application.
>
> ¤ Access does ask Jet (via a Jet API) to create, within the MDB file,
> ¤ some containers for Access to store its own things (forms, reports
> ¤ etc.) - but that does not make Access, a database.
> ¤
>
> Huh?
>
> ¤ I suspect your mistake is in believing that an MDB file is an *Access*
> ¤ file. It is not - it is a *Jet* file, in which Access is able to store
> ¤ its own things (in addition to the standard Jet things).
> ¤
>
> Baloney. It can contain data, code and database related objects that are
> native to the Microsoft
> Access application. An MDB file *is* an Access database.
>
> ¤ A VB program can use a Jet MDB file for database storage; but VB is not
> ¤ Access, and does not require Access to be present in any way, shape or
> ¤ form.
>
> That is, unless you attempt to use functionality that is not supported by
> Jet, but is only available
> through the Microsoft Access application.
>
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)


.

Relevant Pages

  • Re: Any reason why accessing Access should slowdown?
    ... On the MSACCESS / JET OLEDB front, you responded to a query I had about the ... Declared connection to Access database using string based on Jet OLDB ... Set up recordset filter in response to earlier input / selection ... ¤ I am writing a VB6 App using an Access database backend ...
    (microsoft.public.vb.database)
  • Re: Access vs SQL
    ... the Microsoft Jet database engine has been ... > ¤ How about if we say that an .mdb file is an Access file that wraps a JET ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Mock Database in Excel
    ... You don't need the MS Access application to create and/or query a Jet ... You can do all this on the fly using only Excel ... and ADOX (to create the .mdb file) and ADO (use DDL statements to ... Creating an AccessDatabase ...
    (microsoft.public.excel.misc)
  • Re: Dynamic MDB creation for specific formats 2000-2007
    ... If the specific format could be created from the outset - ... the resulting database - if they were - wouldn't care about any of this. ... ¤ If the database is being created on one system which by default creates ... It doesn't matter when accessing the database through Jet ADO or DAO. ...
    (microsoft.public.vb.database.ado)
  • Re: Access vs SQL
    ... of the other things that database products have to do. ... Those technologies all reside in a completely seperate product, MS Jet. ... I suspect your mistake is in believing that an MDB file is an *Access* ...
    (microsoft.public.dotnet.languages.vb)