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

[Jim Lawrence]

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