VB Migration Partner

KNOWLEDGE BASE - Database and data-binding


Previous | Index | Next 

[INFO] ADO-related code in the migrated VB.NET application might not behave like the original VB6 code

We have noticed that ADO objects used through COM Interop may behave differently from how they do in VB6 applications. This malfunctioning may happen, for example, when passing objects stored in Variant variables as arguments to the ADO Recordset’s or Connection’s Open method.

In some cases the problem is caused by referencing the object variable and omitting the name of the default member, in which case explicitly using the default member’s name solves the problem.

As of this writing, however, we haven’t found a general rule to work around these issues. We plan to create a list of malfunctioning cases to be added to the product documentation, so that users can quickly learn how to fix it.

Previous | Index | Next 




Follow Francesco Balena on VB6 migration’s group on

LinkedIn





Read Microsoft Corp’s official case study of a VB6 conversion using VB Migration Partner.




Code Architects and its partners offers remote and onsite migration services.

More details




Subscribe to our free newsletter for useful VB6 migration tips and techniques.

newsletter



To learn more about your VB6 applications, run VB6 Analyzer on your source code and send us the generated text file. You will receive a detailed report about your VB6 applications and how VB Migration Partner can help you to quickly and effectively migrate it to .NET.

Get free advice



A fully-working, time-limited Trial Edition of VB Migration Partner allows you to test it against your actual code

Get the Trial




The price of VB Migration Partner depends on the size of the VB6 application, the type of license, and other factors

Request a quote




Migrating a VB6 application in 10 easy steps

Comparing VB Migration Partner with Upgrade Wizard

Migration tools: Feature Comparison Table

All whitepapers