Re: Replacement for Dao

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: rajas (rajas_at_cox.net)
Date: 05/10/04 

Date: Sun, 9 May 2004 17:44:23 -0700

Roy,
Thanks for the input.

The application (an MFC app) that I am looking at actually works well with
Access2000 - in fact the application checks to see if jet 4.0 is available
and uses AfxGetModuleState()->m_dwVersion = 0x0601; to work around the hard
coding in MFC. However, something in Office 2003 seems to break it.

As I wrote earlier, the application uses Jet database or SQL server. I read
that Jet actually provides ADO support through its ODBC (I am still looking
through examples in ODBC for Autonumber - seems a pain with need for
multiple accessor macros , as well as BLOB support for large text strings -
was straight forward in Dao) and hence ODBC may perform better than ADO.
Have not made a decision yet - but looks like I need to real soon.

"Roy Fine" <rlfine@twt.obfuscate.net> wrote in message
news:uouV1qSNEHA.892@TK2MSFTNGP09.phx.gbl...
> Rajas,
>
> you may have gotten a bit of bad info -- DAO still works, it is MFC that
is
> hardcoded to the DAO 3.5 version. DAO 3.6 works well with Jet 4 database
> versions through Access 2000 for sure.
>
> If you want to move away from DAO, then you should seriously consider
ADO -
> there are capabilities in ADO and ADOX that match DAO, while the ODBC
> support is a bit weak (like not being able to create autonumber column,
and
> not being able to access the @@IDENTITY column, etc...)
>
> regards
> roy fine
>
>
> "rajas" <rajas@cox.net> wrote in message
> news:H2tmc.17865$ph.13348@fed1read07...
> > Hello,
> >
> > I need to 'update' an application that uses MFC Dao database classes -
it
> > appears that this will not work in newer Windows & no longer supported.
> The
> > application uses Access or SQL server depending on the circumstances.
> >
> > What is the best alternative - Still need to use VC 6 (not .Net).
Need
> to
> > taking into account learning curve & 'longevity' of support.
Performance
> is
> > also a consideration - though secondary. Most ADO examples in MSDN
> seem
> > to be .Net or VB, and OLE DB examples are even more limited.
> >
> > I would appreciate any and all input. If there is already a place where
> > this has been discussed - I would appreciate if someone would point me
to
> > it.
> >
> > Thanks
> >
> >
>
>

Relevant Pages

  • Re: Any REAL reason to use ADO vs. DAO?
    ... Your options are limited to ODBC ... and problems when using ODBC in conjunction with DAO. ... There's limitations with everything. ... Once again, DAO or Jet? ...
    (microsoft.public.vb.general.discussion)
  • Re: Fixing table links with ADO
    ... have used DAO. ... Anyone know of a sample of such a routine that ... table links are ODBC connections anyway. ... to Jet via ODBC. ...
    (comp.databases.ms-access)
  • Re: Any REAL reason to use ADO vs. DAO?
    ... download the data via DAO, and trying the same thing via ... ADODB took over 24 hours... ... a localized Access database where a VB5 app (project started ... I understand that the make table queries were Jet, ...
    (microsoft.public.vb.general.discussion)
  • Re: How to enforce subtypes/supertypes in Access 2000?
    ... DAO is the native object model for Jet databases and, as such, is the ... ever need ADO. ... Private Sub SetContactType() ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Speichernutzung von .NET-Anwendungen
    ... und dennoch weiterhin DAO verwenden. ... Neuentwicklungen und die Vorteile bisheriger Techniken gegenseitig ... > Zugriff auf die Jet Engine. ... Technologie bei dem ursprünglichen "DBMS" (Access) mehr besteht? ...
    (microsoft.public.de.german.entwickler.dotnet.vb)