Migrate MS Access Databases to MS SQL Server, Oracle, DB2
Convert Access Applications to Client/Server Architecture
Client/Server Solution
A typical conversion to client/server architecture involves the following steps:
Data Definition Language (DDL)
DDL is generated for the target DBMS that precisely replicates the Access
database design. Your organization's DBA naming standards can be applied to all
generated objects and table spaces specified. Redundant
indexes are ignored and cascade update relationships are enforced. Our tools
normally automate 100 percent of DDL script creation.
For more details about DDL generation and other software features, select Scriptoria for your target DBMS from the Enterprise Tools menu.
Data Population
We provide software or MS SQL packages for easily populating the target DBMS
with MS Access data to support test and production environments.
Query Conversion
Our toolset includes a robust MS Access query conversion facility for MS SQL,
Oracle and DB2 that typically automates 90 percent or more of the conversion of
all Access queries.
For client/server conversions that utilize MS Access as the front-end, queries
are converted for all Reports and non-updateable Forms. All Action queries
(append/update/delete/make table) are converted to stored procedures.
We recommend that any external data sources used by the Access application to
update the database be replaced by ETL or backend processes.
Client-Side Application Conversion
An effective and expedient method for converting Microsoft Access applications
into client/server architecture is the Linked Table/View approach. This
strategy involves the least amount of programming, yet yields high-performance,
highly concurrency applications that require neither user nor developer
re-training.
Our software generates new MS Access “.mdb” applications that integrate all
converted objects, achieving effiicient client/server architecture while
retaining the exact look-and-feel and operation of the original Access
application.
There are some common misconceptions about ODBC versus ADO concerning
performance, security, and reliability. We have successfully implemented the
Linked Table approach at some very techically savvy and security conscious financial institutions,
like Wells Fargo Bank and CitiGroup/Germany whose main concern was hackers
transferring Access databases offsite and cracking them open.
MS Access front-ends can be effectively “locked-down” such that they look and
operate just like any VB or Java program. Advanced application security is much
more involved than just converting to ADO, as illustrated by the MS Access
Application and Sarbanes-Oxley Compliance
white paper.
MS Access applications to client/server using ADO frameworks, like
VB.Net Windows are much more costly to implement and offer
no tangible performance, security, or reliability advantage over
ODBC.
To understand the quality and performance of our Client/server solution,
please Test-Drive the Northwind Traders sample applications.
| 