|
| |
Building a Custom Database Independence Layer
If a large installed user base using a proprietary
database solution creates a migration problem for you, the steps to move
away from this proprietary database are:
-
PowerVista will build a database independence
(DBI) module for your proprietary database.
-
You can start building hybrid applications that
consist of legacy code in combination with a modern graphical user
interface built with PowerVista.
-
After your application has been converted, and you
no longer are using any legacy code, you can execute a simple data
conversion to move your data to a modern SQL solution such as Oracle,
Sybase, Pervasive SQL.2000, Access or Microsoft SQL Server.
One of our customers sells an accounting system for a
vertical market. Their accounting system had a character based user
interface and was built on a proprietary database. They were not able to
use any commercially available tools, hampering their efforts to build a
modern, graphical user interface to their accounting system. With a large
installed base of users using many software modules, it would have been
very difficult to abandon the existing data and build an entirely new
accounting system from scratch. By building a custom database independence
layer to their
proprietary database, they were able to immediately get the benefits of a
modern user interface while still accessing their customer's existing
data. Because PowerVista can access multiple types of databases
simultaneously, their custom DBI is allowing them to transition from the
proprietary database to open SQL systems, on their own schedule.
If you wish to speak to one of our customers about
their experiences with building a custom style layer, please call our sales
department, and we would be happy to set this up.
|