Re: Back-to-front introduction needed

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 07/14/04


Date: Wed, 14 Jul 2004 11:59:12 -0700

Nope. The HHG is more of an architecture book that was written before .NET.
"ADO.NET and ADO Examples and Best Practices is the .NET" version, but it
does not discuss the JET/MDAC/DAO/RDO architecture issues as much.

That's the problem with JET. While it's easy to hand someone your
application .EXE and the .MDB file, you also have to get them to install the
"MDAC stack" on their system that includes the version of JET you used to
create the application. The problem is that they might not be using the same
version and your application might not work with the version that's there.
If you replace their MDAC/JET, their old applications might break. If you
use the version that's there (because it's newer), your application might
not work. Sure, MDAC has gotten better over the years and these problems
aren't always a problem--only about half the time now... ;)

This (and a dozen other reasons) is why I don't recommend JET.

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"John Dann" <news@prodata.co.uk> wrote in message
news:cgp9f0hu68lo6rlc5vlpe57n2ufkkdbdmi@4ax.com...
> On Tue, 13 Jul 2004 10:18:30 -0700, "William \(Bill\) Vaughn"
> <billvaRemoveThis@nwlink.com> wrote:
>
> >I would recommend my Hitchhiker's Guide to you but it also assumes you're
> >working with a database engine of some kind.
>
> Many thanks  Bill for the pointer, but I couldn't see a VB.Net
> version.( I'm inclined to  think -rightly or worngly - that there's
> probably enough to learn just focusing on the .Net versions of VB and
> ADO without perhaps the potential for confusion that including
> descriptions of and migration advice for earlier technology versions
> might bring.) But maybe a VB.Net version does exist?
>
> >There is nothing to stop you from using
> >ADO to store the data (in XML) locally.
>
> I understand that point and it might well have some application in my
> project but all things considered I think I really need to aggregate
> all of my large volumes of data in a formal database
>
> >However, the advantages of using a
> >storage engine like SQL Server (MSDE) or JET (for personal systems) are
> >manifest. The engine does all of the physical IO in binary. It handles
data
> >security, and permits you to backup and protect the data in a number of
> >ways--you would have to write all of that yourself if you choose not to
use
> >a DBMS engine. The DBMS also permits you to organized the data in
relational
> >tables and fetch it with automatically created indexes and unique keys.
> >While an in-memory database is fast, you have to write a lot of code to
> >implement and support it. Consider that MSDE makes heavy use of RAM to
cache
> >most frequently used data and procedures.
> >
>
> OK, thanks, the mist is slowly starting to clear. I can see - I think
> - that say an Access database environment can consist of three
> components:
>
> 1. The mdb file that contains the actual data'
> 2. The JET engine to provide the functionality to query and maintain
> the database;
> 3. The Access application to provide a friendly user interface to the
> database;
>
> But in the context of distributing a new program that can create and
> use an Access-type database, where does the JET engine fit in. Is this
> something that I have to include specifically in the distribution? Or
> is it an integral part of the .Net framework?
>
> Thanks
> John Dann
>
> PS I noticed that part of your VP WL page (trends and maxmin) isn't
> updating. One of the profiles hasn't inadvertantly been turned off
> has it?


Relevant Pages

  • Re: ADO vs DAO vs ADODB
    ... ADODB is simply a object reference to the ADO library. ... ms-access is a developers tool, like VB, or C++. ... server, oracle, or the default "file based" JET data engine. ... The mdb file format is based on the JET database engine. ...
    (microsoft.public.access.formscoding)
  • Re: SQL Sum producing rounding error on currency fields
    ... and that the fault is with the query engine. ... The new database did NOT show the .0999 result, ... confirms the fault is with the JET 3.5 engine used by Access 97. ... Dim rs As DAO.Recordset ...
    (microsoft.public.access.queries)
  • Re: Databases - DAO and ADO
    ... Jet or ODBC? ... DAO or ADO? ... While I wait for additional books to arrive (just bought VB6 Database for ...
    (microsoft.public.vb.general.discussion)
  • Re: Use DAO or ADO?
    ... tables to a jet backend to open a ado recordset. ... will ALSO work for mysql, oracle and sql server if I take that sql ... engine that they don't understand who want to avoid Jet at all ...
    (comp.databases.ms-access)
  • Re: [Access2003, VBA] Use DAO or ADO?
    ... tables to a jet backend to open a ado recordset. ... Because one might have chosen to use ado in place dao in their ... You gain sql neutral code. ... engine that they don't understand who want to avoid Jet at all ...
    (comp.databases.ms-access)