Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

In a VB 6.0 to VB.NET project without ADO Data Binding, how does the automatic upgrade work?

April 26, 2017Ado automatic Binding Data project upgrade VB VB.NET

0

Posted

In a VB 6.0 to VB.NET project without ADO Data Binding, how does the automatic upgrade work?

1 Answer

0

Posted

An application falls into this upgrade scenario when its project references Microsoft ActiveX Data Objects but does not contain an ADO Data Control. In this case, all data access is managed directly at run time. The automatic upgrade of a project that accesses a database without the use of data binding does not require changes in the upgraded code. The upgrade wizard automatically adds the reference to Microsoft.VisualBasic.Compatibility library, which contains ADO. All ADO code works without any modifications and has the same behavior as in the original Visual Basic 6.0 project. However, there is a difference between the upgraded code and the original source code with respect to how a field in a recordset is accessed. In Visual Basic 6.0, it is common to access fields using the shorthand coding convention RecordsetName!FieldName. In Visual Basic .NET the code needs to be expanded to resolve the default properties.