Re: why should'nt i use dao 3.51 for this?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Chris Barber (chris_at_blue-canoe.co.uk.NOSPAM)
Date: 02/08/04 

Date: Sun, 8 Feb 2004 17:54:14 -0000

DAO whilst being fast and targeted directly to MSAccess is just that -
targeted ONLY for MSAccess.

If you use the comparable ADO code then you can move the DB around and of
course upscale to MSDE and SQL Server as required.

However, if DAO and MSAccess is *all* that are concerned with for the short
term future then by all means use it. As long as there is a W32 OS I'm sure
that DAO will be usable on it (as packaged with an application install).

ADO does however allow you to code against any database secure in the
knowledge that your code will be the same irrespective of the database
itself (in most cases). It's also clear that ADO has already replaced DAO as
the mechanism for database access and as such if you want to stay current
then you should definitely consider it even if you are only using it against
MSAccess. At the end of the day, ADO is only a wrapper anyway and uses Jet
behind the scenes to access MSAccess databases (if you us the Jet OLEDB
connection string of course).

In your scenario there are only two reasons for a move to ADO - your own
personal coding development and maintainability (since other developers at
that time may be 'unfamilar' with DAO).

Chris.

"scuuby" <nospam4scuubydu@slingshot.co.nz> wrote in message
news:opr2mnnbrs8pz0u4@news.slingshot.co.nz...

hi guys,
- ok so dont spit the dummy yet because
for me this is a legit question...

i am going to write a little prog to run
on 9x system for a SINGLE USER.
that means it will NEVER see more than
a single user ever and i want to keep
it small compact and simple. it will
never go outside New Zealand so its
english only and record count will not
exceed 20,000 per table (around 50-ish)
per year and new db for every year so
apart from the you must keep up with
technology freaks out there...

does anyone have an "outstanding" reason

...why i should NOT use dao 3.51 for
this hopefully tiny application?

thanks in advance

Scuuby 

-- 
=================================
nospam4scuubydu@slingshot.co.nz
remove nospam4 from return email to reply
=================================

Relevant Pages

  • Re: Access 2007 and VB
    ... "unrecognized database format" ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)
  • Re: Access 2007 and VB
    ... and link to the download as a non expert some ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)
  • Re: Access 2007 and VB
    ... "unrecognized database format" ... There is a bit of confusion with ADO access to the new MSAccess ACCDB ... You could reference "DAO". ...
    (microsoft.public.vb.general.discussion)
  • Re: Knowledge Base Help Not working
    ... Database is a DAO object. ... both Access 2000 and 2002 use ADO. ... Microsoft DAO 3.6 Object Library, ... For example, to ensure that you get a DAO recordset, you'll need to ...
    (microsoft.public.access.formscoding)
  • Re: why shouldnt i use dao 3.51 for this?
    ... DAO whilst being fast and targeted directly to MSAccess is just that - ... if DAO and MSAccess is *all* that are concerned with for the short ... ADO does however allow you to code against any database secure in the ...
    (microsoft.public.vb.database)