DAO to ADO and stored procs

Hello,


We are moving an entire project from DAO (Diamond access) to ADO.

The Database is MS Access 2000 and nothing is changed from the database side.
We encounter lots of problem on converting TDaoStoredProc to TADOStoredProcs, with several error messages (Errors are in french, so I don't mention them here).

The problems are mainly queries with params, complicated queries (calculations or so), queries with linked tables.

We changed nothing in the database itself, the DAO version is running well and is in use.

The conversion seems easy, we have the same kinds of components, I'm sure we don't have errors in the params definition or so...so why do we have so many problems ?

Does anybody have some tips or experience about this conversion ?

Thanks a lot

Best regards

Frédéric
.

Relevant Pages

  • Re: Run action query in back-end from front-end database
    ... whatnot in the back end database. ... The queries are housed in the back end ... The reason I have the upload tables in the back end is that it will be on ... Rick's code uses DAO, and Access 2000 doesn't have a reference set by ...
    (microsoft.public.access.externaldata)
  • Re: Run action query in back-end from front-end database
    ... Rick's code uses DAO, and Access 2000 doesn't have a reference set by ... With any code module open, select Tools | References from the menu bar, ... consider putting them in a temporary database. ... The reason I have many queries in the back end database is because it does ...
    (microsoft.public.access.externaldata)
  • Re: Run action query in back-end from front-end database
    ... ADO is a more generic approach. ... Since DAO was designed specifically for use with Jet databases, ... And I still don't buy your argument about why you have the queries in the ... whatnot in the back end database. ...
    (microsoft.public.access.externaldata)
  • Re: Startup Question based on date
    ... Assuming that you upgraded from ACCESS 97, then you need to set a reference ... to DAO library in your ACCESS 2002 database. ... > maximize the startup form and not run all of the queries. ...
    (microsoft.public.access.modulesdaovba)
  • Re: VBA CODE - ADODB
    ... You do not want to use DAO with Access or anything else at this time. ... A second reason is there's no advantage that ADO is going to give you ... It all depends on the code and queries. ... > most VB/DB code is so God-awful that the database layer doesn't matter. ...
    (microsoft.public.vb.general.discussion)