The best available tools to perform code migrations from a source database or Spark application to Snowflake.

Spark Scala
Spark Python
SQL Server

Data Solutions
The premier productivity workbench designed and optimized for teams using Snowflake.

Translation with SnowConvert
Edit, Debug & Deploy
Automated Test Case Generation
Metadata Analysis
Source Code Management

Get Started
There are countless ways to take advantage of BlackDiamond Studio and SnowConvert.

Migration and Other Snowflake Services
Get Up and Running with Snowpark
Using the SnowConvert Trial
Build a Cross-Platform Object Inventory

Monetize Your Data

We Are GAP Mobilize
Free Assessment Tool

Error Handling Transformation


Error Handling Transformation for VB6 to .NET

Visual Basic 6.0 and the .NET languages have different error handling techniques; while VB.NET is able to support a small subset of VB6 error handling keywords, C#.NET is not.

Also, VB6 features in-code labels that can be used to create confusable “jump” patterns. These patterns are complex to read in VB6 and need to be removed from the resulting code for the sake of maintainability.

The Visual Basic Upgrade Companion is able to remove unstructured “spaghetti code” and convert it to structured .NET statements. All unused labels are removed from the resulting code, plus the most commonly used “On Error” patterns are currently recognized and replaced for native .NET equivalent “try … catch” blocks.

As part of the full conversion of the Visual Basic 6 Error handling schema (On Error ... Goto) to .NET, it is also necessary to convert the Err Object.

The following VB6 extract shows a simple usage of the “On Error” statement to avoid a possible division by zero. The flow control of this source code extract will jump to the “ErrorHandler:” label in case there is an arithmetic error.

Original VB6 source code

describe the image

The Visual Basic Upgrade Companion is able to generate VB.NET source code using the .NET “Try Catch” blocks by applying special refactor techniques, as well as the same error management patterns from VB6 if needed. If the resulting language is C# the “try catch” generation is mandatory.

VB.NET code generated by the Visual Basic Upgrade Companion

VBUC generated code 


C#.NET code generated by the Visual Basic Upgrade Companion

Csharp generated code
Talk To An Engineer

Call us today at 1-425-609-8458 or email us at