VBUC
Visual Basic Upgrade Companion. VB6 Converter for .NET & Web.

VB6
ASP
.NET7 supportDownload Now

WebMAP
Cloud Application Migration Tools Transform Desktop Applications

C#
Silverlight
Access
VB.NET
PowerBuilder
Winforms
ASP.NET Web Forms

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

Oracle
Spark Scala
Spark Python
SQL Server
Teradata

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

Time to Mobilize
Free Assessment Tool

Solving the legacy database problem

by John Browne, on Mar 1, 2018 6:00:00 AM

connx.jpg

Not every legacy app has a database connection but I've yet to see one of any size or value that didn't.

That said, we here at Mobilize have largely left the database/data layer alone--part of the beauty of our migration tools (like VBUC) is that they play so nicely with your existing DB code, converting RDO, DAO, and ADO to ADO.NET for easy connection to SQL Server or even Microsoft Access. However, that's only one piece in the legacy DB puzzle. 

Well now we have a bigger solution, thanks to our newest partner CONNX. Part of Software AG, CONNX has drivers for a variety of databases (IMS, RMS, DB2, VSAM, Adabas, and a zillion more) for synchronization, replication, connection, and more. As of today, Mobilize.Net is a reseller for CONNX products. You can see the full list of adaptors here.

Virtual connections, federating data, and more

Imagine, if you will, our demo app Salmon King Seafood--VB6 with a Microsoft Access database behind it. SKS knows about orders, customers, products, and inventory. What it doesn't know about is customer credit history. That information, for the sake of this example, is stored in an ERP system that uses a DEC RMS database. 

It's pretty quick and easy to modernize SKS from VB6 to either .NET (keeping it on a laptop) or even HTML and that's cool and all but it doesn't help the sales reps know if they need to chase a slow-pay customer before submitting a new order from said deadbeat. Up to now, the finance department has been trying to keep the sales team up to date on who's current and who's 90 days behind via email, but it has not been a successful effort. Sales reps, hungry for commission, take orders from customers who are already over their credit limit. 

So with CONNX, let's add "Credit_limit", "Current_balance" and "Days_past_due" fields to the Customers table in SKS, and connect those two fields to the database using a CONNX RMS adaptor. Now in real time the sales team will see, before processing an order, whether the customer should be greeted with a smile or a frown. 

Modernizing your apps with Mobilize.Net tools and federating all your data with CONNX means any app can access any data, regardless of where it resides or in what format. 

And that's got to be a good thing.

Topics:CONNXdata modernization

Comments

Subscribe to Mobilize.Net Blog

More...

More...
FREE CODE ASSESSMENT TOOL