Re: vb5 versus vb2008

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Ah, my advice is to learn the VB5 application's functions. Once understood learn how to build a VB.NET application and create one that performs the same operations. While some VB6 code can be converted automatically by VS2008, not near all of it will be usable. No, DAO is not supported and has not been for some time. As Markus said, COM-based ADO is different from ADO.NET (as I discuss in "ADO and ADO.NET Examples and Best Practices"). I've found that many (far too many) of the code blocks written in ADO do not translated well to ADO.NET--I generally started over. You'll also find that JET/Access databases are also being phased out. I suggest investigating SQL Server Compact or Express editions. These two (very different) DBMS engines are free, lightweight and a good substitute for JET.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message news:%23zET5ZPtIHA.524@xxxxxxxxxxxxxxxxxxxxxxx

"Markus Diehl" <markus@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23kKaeiMtIHA.4876@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

was using this piece of source since long in VB5. Now we have to transfer
it
into VB2008 and getting a lot of compiler errors. I got mentioned, that
DAO
don't work in VB2008. Is there somebody out there who can assist me??

<snipped>

You are correct DAO is NOT supported with VB2008.
You have two choices.
1) Convert the DAO to ADO. This is best done with the existing VB5 project.
And then attempt to migrate your code to VB2008. You can use ADO in VB2008.
2) Or change the migrated DAO code in VB2008 to use ADO.Net, skipping the
conversion to ADO.

Note: ADO and ADO.Net are very different access libraries, don't let the
similarity in names fool you. ie, converting to ADO and then to ADO.Net will
not ease the conversion in any useful way.

The same can be said for VB2008 and VB5.

But you need to post to a "dotNet" newsgroup. These newsgroups will have
"dotNet" in the title. This newsgroup, and any others with ".vb." in the
title, is populated by users of 'classic VB' (VB6 or lower).

hth
-ralph



.

Relevant Pages

  • Re: vb5 versus vb2008
    ... You are correct DAO is NOT supported with VB2008. ... Convert the DAO to ADO. ... This is best done with the existing VB5 project. ... not ease the conversion in any useful way. ...
    (microsoft.public.vb.database)
  • Re: Newbie help. ADO ADO?
    ... As you are using VB5, DAO is the data access method of choice for you. ... >>I am new to databasing and am confused about dao and ado. ...
    (microsoft.public.vb.database.dao)
  • Re: Access 2000 Datenbank in V.B. 5.0
    ... > Access 2000 erstellt worden ist.Gibt es gegebenenfalls Datenbanktreiber? ... Du kannst auch in VB5 Jet-Datenbanken öffnen/bearbeiten. ... Für DAO 3.6 sowie auch für ADO solltest Du auf Deinem ...
    (microsoft.public.de.vb.datenbank)
  • Re: DAO and Access 2000
    ... > I have a few quick questions regarding DAO and Access ... > I am just now beginning to make the conversion to Access ... > Should I be learning ADO and converting my DAO code to ADO ... JET have DAO as Native Library, so you force JET to do double ...
    (microsoft.public.access.modulesdaovba)
  • DAO and Access 2000
    ... I have a few quick questions regarding DAO and Access ... I am just now beginning to make the conversion to Access ... Should I be learning ADO and converting my DAO code to ADO ... I cannot seem to find any DAO help file information in ...
    (microsoft.public.access.modulesdaovba)