Data1 object conversion on .NET upgrade 
Author Message
 Data1 object conversion on .NET upgrade


I am trying to upgrade an older VB3-6 application I wrote and it is not
recognizing the Data object I had on all my forms.  It therefore does not
recognize any  of the commands like Close, Recordset, DataBaseName,
RecordSource... etc. etc.

Does anyone know a way of .NET fixing these problems?

Am I forced to re-write all the data connectivity and SQL code?
If so then the upgrade path is a waste of time.   I might as well re-write
the entire application.

Hopeful of help


Tue, 28 Sep 2004 03:48:38 GMT  
 Data1 object conversion on .NET upgrade
It's probably easier to rewrite the application using the new .Net data
access method, but to fix your problem you probably just need to add a
reference to the old ActiveX data Objects ADODB.dll that you use in your vb6
applicaiton.  You can do this through the reference folder in your project

I used the converter and then found out that it would have been
better/faster to use the data access built into the framework.
(System.Data)...I have a huge applicaiton and it was a pain to convert the
old code to the new framework but it will run cleaner and you don't have to
carry around the abodb.dll file when you deploy your app later.


Tue, 28 Sep 2004 03:56:27 GMT  
 [ 2 post ] 

 Relevant Pages 

1. VB6 to .Net Conversion/Upgrade

2. Data1.UpdateRecord vs. Data1.Recordset.Update

3. Upgrading to VS.Net 2003 from VS.Net 2002

4. Upgrade from Visual Basic 6 webclasses to VB.NET/ASP.NET

5. debugging upgraded component in

6. VS .NET 2002 upgrade to 2003 and CR.NET

7. Conversion of VB.Net App to ASP .Net App

8. Crystal Reports 8.5 (VB6) to Crystal Reports NET (VB.NET) conversion

9. Window Service upgrade to VB.Net 2003

10. upgrading to VS.Net 2003

11. VS.NET 2003 upgrade options

12. how to buy upgrade from vs .net 2002


Powered by phpBB® Forum Software