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

William Benson vbacreations at gmail.com
Fri Jan 24 14:11:51 CST 2014


You are only correct if you consider access as an application running in
its on thread. I am pretty sure that when I use Excel and ADOX, ADO, and
JRO to build set relationships and control the contents and behavior of
tables and other objects in Access that I am NOT using DAO at all.
On Jan 24, 2014 10:17 AM, "John W Colby" <jwcolby at gmail.com> wrote:

> >DAO is more for power users than for real developers. I am not sure I
> would have got into ADO if there had been no other way.
>
> 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
>
> Reality is what refuses to go away
> when you do not believe in it
>
> On 1/24/2014 1:32 AM, Jim Lawrence wrote:
>
>> Hi Charlotte:
>>
>> DAO is more for power users than for real developers. I am not sure I
>> would have got into ADO if there had been no other way.
>>
>> But Access is one of the best ways to at least learn the basics of
>> database design...it truly has (or is that had) one of the best data
>> modelling capabilities.
>>
>> I hope you are enjoying your job of teaching relational database to
>> uninitiated. Maybe you could, at some time in the future, be also giving
>> advanced classes?
>>
>> Keep up the good work.
>>
>> Jim
>>
>>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list