[AccessD] Problem of a listbox's response on network... Part 1

Fri Apr 10 05:27:26 CDT 2015

  Yeah but it's still fundamentally JET.  Outside of a few new data types,
there were no other changes.

Jim. 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Stuart McLachlan
Sent: Friday, April 10, 2015 12:03 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Problem of a listbox's response on network... Part 1

Just a minor point. JET (Joint Engine Technology)  was used up to 2003
(.mdb)

2007 onweards (.accdb) was ACE (Access Connectivity Engine)  but is now
called Access 
Database Engine (unabbreviated).

-- 
Stuart

On 9 Apr 2015 at 21:22, Jim Dettman wrote:

> <<
> Seriously, where is the final analysis on this? John C is saying DAO
> is present at all times directing traffic, yet Jim is saying that ADO
> is faster than DAO. >>
> 
>  No, the first is incorrect.  ADO does not run through DAO.  They are
>  two
> separate and distinct things.
> 
>  As for the second, for all but JET based DB's, ADO is usually faster.
>  Part
> of that is ADO was designed to talk to a multitude of data sources, so
> you have a large amount of control over the cursor in regards to type,
> location, etc.
> 
> But with a JET based data source, DAO is faster than ADO.  The reason
> for that is what you'll find with ADO, your shoe horned into only a
> few "heavy weight" cursor types as soon as you talk to a JET DB
> despite what you ask for.
> 
> DAO is more tightly integrated with the JET dbEngine as a whole.  ADO
> has to jump through some hoops to do things because it's a generic
> data lib and was not specifically written to be used with JET, where
> as DAO was written only for JET and a handful of ISAM data stores.
> 
> Jim. 
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of Bill Benson Sent: Wednesday, April 08, 2015 05:26 PM To: Access
> Developers discussion and problem solving Subject: Re: [AccessD]
> Problem of a listbox's response on network... Part 1
> 
> Very interesting. My follow up would be, how much data can you fit
> into your sportscar versus the 18 wheeler? I would say the sportscar
> can get there faster but needs to take more trips...
> 
> Seriously, where is the final analysis on this? John C is saying DAO
> is present at all times directing traffic, yet Jim is saying that ADO
> is faster than DAO.
> 
> I am now thoroughly confused.
> 
> On Wed, Apr 8, 2015 at 11:41 AM, Jim Lawrence <accessd at shaw.ca> wrote:
> 
> > Hi Janet:
> >
> > Here is some questions answered about using ADO...1 of 3
> >
> > Regards
> > Jim
> >
> > ----- Original Message -----
> > From: "Jim Lawrence" <accessd at shaw.ca>
> > To: "Access Developers discussion and problem solving" <
> > accessd at databaseadvisors.com>
> > Sent: Friday, January 24, 2014 11:40:10 PM
> > Subject: Re: [AccessD] Problem of a listbox's response on network...
> > Part
> 1
> >
> > Hi Mark:
> >
> > It does depend on where your program is pulling data.
> >
> > There is no substitute for speed when a local DAO connection is
> > pulling and displaying a single record or small group of records
> > from a local MDB database but have a DAO connection download 15K of
> > records from a remote server and fill a table with the results...
> >
> > An ADO connection can do that in one to two seconds. It is like
> > comparing a sports car to an 8 wheel semi, when it comes to moving
> > data.
> >
> > In addition, shut down the central MDB database a few times through
> > out the day and you would be lucky not to corrupt your database. ADO
> > type connections expect delays...rebooted a MS SQL and when it
> > restarted the
> ADO
> > data stream continued processing.
> >
> > There are trade offs for sure; DAO is great for small 2 to a 50
> > maximum number users, in stable environments but if you are using
> > industrial sized data, ADO is the only way to go.
> >
> > Jim
> >
> > ----- Original Message -----
> > From: "Mark Simms" <marksimms at verizon.net>
> > To: "Access Developers discussion and problem solving" <
> > accessd at databaseadvisors.com>
> > Sent: Friday, January 24, 2014 6:55:13 PM
> > Subject: Re: [AccessD] Problem of a listbox's response on network...
> > Part
> 1
> >
> > Not to mention that ADO is SLOOOOWWW-D-O.
> > Omigosh, I love the speed of DAO. Yes, AC2010 is a bit slower than
> > AC2003....but so-be-it.
> >
> > > Excuse me?  DAO is the database engine AND (more importantly)
> > > object model for all of Access.  DAO is for programmers who need
> > > to program to the metal of forms, querydefs, controls and so
> > > forth.  If you use ADO, it is all a layer on top of DAO.
> > >
> > > I am not disagreeing that ADO has its place, but "for power users"
> > > is just plain wrong.  There is not an electron that flows through
> > > Access that DAO does not steer.
> > >
> > > John W. Colby
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com