VB Migration Partner

KNOWLEDGE BASE - Forms and controls


Previous | Index | Next 

[INFO] Minor differences between VB6 and VB.NET RemoteData controls

VB.NET doesn’t directly support any flavor of the Data control, including the RemoteData control based on RDO technology. VB Migration Partner provides a custom version of the RemoteData control, which is virtually identical to the corresponding VB6 control, except for the following minor differences:

  1. When the Refresh method is invoked, the VB6 RemoteData control fires the QueryCompleted event, whereas the .NET control fires the QueryCompleted and then the Reposition event.
  2. When you reach the BOF or EOF condition, the VB.NET control disables the Previous or Next button, respectively, whereas the original VB6 control never disables any button.
  3. When the parent form is loaded, the .NET RemoteData control fires the QueryCompleted and the Reposition events, whereas no event is fired by the original VB6 control.
  4. The .NET control can raise the MouseDown, MouseMove, and MouseUp events, whereas the original VB6 control never fires these events.
  5. When you change the DataSourceName property via code and the invoke the Refresh method, the VB6 control raises the QueryCompleted event, whereas the .NET control fires the QueryCompleted and the Reposition event.
  6. If the BOFAction property is set to 0, the first record is the current record, and the end user clicks on the Previous button, then the .NET control fires the Validate and Reposition event. No event is fired by the original VB6 control in the same circumstances.
  7. If the EOFAction property is set to 0, the last record is the current record, and the end user clicks on the Next button, then the .NET control fires a Validate and a Reposition event. Under the same circumstances, the VB6 control fires the following sequence of events: Validate, Reposition, Validate, Reposition. However, the VB6 control fires this sequence only the very first time the button is clicked since the form is loaded; all subsequent clicks don’t fire any event. (This is probably a VB6 quirk.)
  8. If you modify the contents of a TextBox (or another similar control) bound to a VB6 RemoteData control and the move to a different record, the following events are fired: Validate (with Action=13), Validate (with Action=3), and Reposition. In the same circumstances the .NET control fires only two events: Validate (with Action=3) and Reposition.
  9. In case of composite errors, the VB6 RemoteData control can fire multiple Error events. Conversely, the VB.NET control always fires a single Error event.
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