Re: Cannot open Access table with ADO or BDE/ODBC


Desktop databases do such things, in opposition to RDBMS, because they
are designed for small databases and can usually (but not always)
afford to fetch all the data.


This statement is almost totally wrong. In ADO whether all records fetched
in memory or not is controlled by Cursor Location property and doesn't
depend on DB backend at all.


.

Relevant Pages

  • Re: Why not use DAO?
    ... You have been refering to DAO vs. ADO when these two things (in the context ... you must have ALREADY used a provider to get to. ... interface for working with JET databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... Happy Christmas an fine holidays for you too. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... Don't listen to those who say something about your English. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... To me your opinion sure does mather, cause as i am not a native English ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... interface for working with JET databases. ... no discussion about that (DAO was also faster as classic ADO) ... more universal provider so ofcourse DAO wil outperform ADO in most ... i just wanted to make clear that you should compare these ...
    (microsoft.public.dotnet.languages.vb)