VB Migration Partner

KNOWLEDGE BASE - Forms and controls

Previous | Index | Next 

[PRB] The UpDown control can affect the wrong property of its buddy control

As of this writing we haven’t found a reliable way to decode the value of the UpDown control’s BuddyProperty property stored in .frm files, therefore in some cases VB Migration Partner might migrate this property incorrectly.

As a reasonable guess, by default the BuddyProperty property points to default property of its buddy control, for example the Text property of a VB6TextBox control or the Caption property of a VB6Label control. In most cases, this guess is correct and no extra step is needed.

If the guess is wrong – that is, the BuddyProperty should reference a nondefault property – you can remedy by inserting a WriteProperty pragma in the form being migrated:

        ' set the BuddyProperty point to the buddy's Value property
        '## UpDown1.WriteProperty BuddyProperty, "Value"
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