VB Migration Partner

KNOWLEDGE BASE - Database and data-binding

Previous | Index | Next 

[PRB] The migrated VB.NET has a “Name ‘xyz’ is not declared” compilation error

VB6 controls ignore the value assigned to the DataSource property if the value doesn’t correspond to an existing data source. Conversely, a control whose DataSource property doesn’t point to an existing object prevents the VB.NET application from compiling. The error message reads

    Name 'xyz' is not declared”

where xyz is the value assigned to the DataSource property.

The workaround is trivial: just fix the problem in the VB6 application by blanking the offending DataSource property. It is clearly a logical error in the original application and we don’t consider this as a VB Migration Partner’s shortcoming.

Previous | Index | Next 

Follow Francesco Balena on VB6 migration’s group on


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.


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