Re: Help with converting DAO to ADO

Robert,

If you use an MDB with ODBC to connect to SQL Server (or other
ODBC-compliant database), you _will_ be using Jet behind the scenes... all
the Queries are Jet Queries, modified by Jet/ODBC except as noted later and
the data will pass through Jet <---> ODBC <---> server. You can use
Passthrough Queries which Jet "leaves alone", but they are typically not
updateable. But, no there will be no scalability problems from using Jet.

You would not be using Jet, even behind the scenes, if you created an Access
project, ADP, but even my ADO-loving friend Lyle no longer does ADPs. I have
worked with ADP, but found nothing that appeared to me to make them better
than MDB and a few things, including classic ADO, that required climbing a
learning curve.

Larry Linson
Microsoft Access MVP


"robert d via AccessMonster.com" <u6836@uwe> wrote in message
news:5c00192105204@xxxxxx
Thank you, Larry.

This information along with my other posts will provide me with a solid
basis
for strongly supporting Access as a development environment for a
front-end,
which, oh by the way, has a native database known as Jet, but which will
not
be used in this implementation (SQL Server) so there are no concerns about
scalability, etc.

Larry Linson wrote:
But, I'm trying to anticipate what this
prospective client might accept as
alternatives if I can't convince them
that my front end is suitable.

Perhaps it would be best to concentrate on convincing them that your front
end _IS_ suitable?

I thought about telling them that I will
convert it to VB6. But I'm not sure
how the data connections would work
to SQL Server. With VB6 can I use DAO
to connect to SQL Server?

If I didn't know you were grasping at straws just to try to win the
contract, I would ask "What do you expect to gain from converting to VB6?"
There'd be a good deal to be lost, and, likely, nothing to be gained from
such a conversion. It would certainly be the question I'd ask if a client
told me they wanted to convert an Access front end to VB6.

You can see a presentation that I did for my user group on the subject ot
Access versus classic VB as a front-end for database applications at
http://www.appdevissues.com/downloads.htm. It may provide some answers you
can use.

VB6 is now, AFAIK, "out of support". It was superceded by the first
version
of VB.NET, and recently the third version of VB.NET was released (as part
of
Visual Studio 2005).

Yes, you could use DAO with VB6 (I am reasonably certain that the DAO 3.6
library is there), but be aware that the VB community "drank the ADO
Kool-Aid" to a much greater extent than the Access community did, so you
may
have to rely on VB5 examples.

Also, what if I have them fairly convinced that my
app will do the trick as it currently is developed,
only to have someone ask me if my data access is
via DAO or ADO. I think if I say DAO, it'll be
counterproductive at that point.

Allen has already given you the points to cover showing why DAO is the
appropriate choice. You could add that "knowledgeable Microsoft insiders"
including the Product Manager for ADP and ADO for a previous version of
Access now recommend MDB-DAO-Jet-ODBC-server database as being generally
preferrable to ADP-ADODB-server database.

Larry Linson
Microsoft Access MVP

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200602/1


.

Relevant Pages

  • Re: Im very confused about the different databases!
    ... There's DAO, ADO, ADO.NET, Jet, SQL, SQL Server ... What database & version comes with VB6 LE? ... What is the most current database that I can use with VB6 LE? ... Why isn't Jet or whatever VB6 LE uses listed in Add-Remove Programs? ...
    (microsoft.public.vb.general.discussion)
  • Re: Database Connectivity
    ... Never was Jet mentioned anywhere at anytime. ... >> Microsoft Access Database Solutions, with not a single mention of Jet. ... front end, and the underlying database engine, JET. ... like SQL Server, Sybase, MySQL, etc. ...
    (comp.lang.python)
  • Re: Duplicate Values Question
    ... My general approach when working with SQL server does NOT include the use of ... If you think that Access 2007 means that Jet ... database code will remain the same forever... ... constraints correct and maintain the data integrity... ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Database has gigantic size
    ... DAO is simply the direct interface to JET. ... this then is exactly why the database grows so large. ... Why were updates within recordsets so ...
    (microsoft.public.vb.database)
  • 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)