 |
Convert MS Access Databases to DB2 ™
and Access Applications to Client/Server, ASP.Net, Java
Scriptoria for DB2™ is an Enterprise quality database migration and application conversion toolset for Microsoft Access.
|
 |
Scriptoria for DB2™ Features |
| Data Model Conversion |
|
-
Access names are automatically renamed to conform to DB2 naming rules. Assigned
names may be replaced by any valid DB2 name. Quoted identifiers are also
supported.
-
All Access data types, including AutoNumber and OLE Objects are supported.
Equivalent DB2 data types can be assigned to individual columns (ex. VARCHAR
for one column and CHAR for another).
-
DATE or DATETIME types can be assigned to individual columns based on table data. MS Access Memo types, which default to DB2 BLOBs, can be assigned with more efficient VARCHAR types. You are presented a list of all Memo fields and their associated maximum lengths based on table data. The default VARCHAR lengths can be adjusted for expected growth.
Access Default Values that do not conform to DB2 rules for specifying defaults
are converted to DB2 triggers.
-
Access Validation Rules are converted to DB2 CHECK constraints or triggers when
appropriate. Validation Rules that specify user-defined Validation Text
messages are implemented using triggers.
-
Foreign-Keys, including cascade update, are fully implemented. Note that the
cascade update property is ignored when the parent table primary key is an
AutoNumber (non-updateable) field.
-
Primary and unique keys and nullable unique indexes are created as specified by
the Access design.
-
Design flaws, like redundant indexes and unnecessary cascade update constraints are
detected and optionally corrected.
-
Missing Primary Keys report shows tables that do not specify primary keys and
will therefore not be updateable using ODBC. Primary keys may be automatically
generated.
-
DB2 table spaces are optionally assigned to tables, indexes and LOBS.
-
Conversion warnings and errors are logged in an Access table for later review.
| Export MS Access Data to DB2™ |
|
-
Data extracted from Access tables is converted to DB2 Load/Import compatible
files.
-
DB2 table data can be migrated using a generated DB2 script or from within
Scriptoria, which invokes the DB2 Load/Import API.
-
Data can be loaded without recreating table definitions.
-
To obviate load errors, foreign key constraint checking is deferred until all data is loaded.
-
Identity and Sequence Start values are reset to reflect current Access Auto Number values.
-
Displays complete DB2 import/load log information
-
Load time is minimized for MS Access tables containing Memo and OLE Object data.
| Convert MS Access Query Definitions to DB2™ |
|
- All Microsoft Access Query Definitions are translated into DB2 views and/or procedures including Crosstab
(pivot table), parameter queries, and multi-table joined updates and deletes.
- MS Access VBA built-in functions, like IIf, Format, DLookup are converted to equivalent DB2 functions or user-defined functions we provide.
- Sub-queries are implemented using DB2 table expressions (derived tables).
- DB2 views and procedures are automatically recompiled when MSAccess/DB2 table structures are changed.
- Case-Sensitivity Assistant identifies queries that may have case-sensitivity
issues and enables developers to enforce consistent case rules for accurate
post-conversion results.
- Over 90% of Query Definitions compile without error. Most problems are easily corrected by modifying the Access query. The Trouble-Shooting section of the Developer's Guide provides detailed problem explanations and work-arounds.
| Convert MS Access Applications to Client/Server Architecture |
|
- New MSAccess applications are generated that integrate all converted DB2 objects while retaining the exact look-and-feel and functionality of the original
application, thereby achieving efficient client/server architecture.
- Test drive the Northwind Client/Server demo.
| Convert MS Access Applications to ASP.Net / AJAX.Net |
|
- ASP.Net WebForms are generated from MS Access Forms that employ AJAX.Net Extensions.
- SQL Server Report Definition Layout files and/or Crystal (Business Objects) Report Definitions are generated from MS Access Reports.
- SQL Server procedures are generated from all Form and Report Record Sources as well as any Combo/List Boxes Row Sources.
- SQL Server procedures are generated for inserting, updating and deleting form data. The update and delete procedures implement optimistic concurrency and insert procedures return any generated Identity values.
- A Switchboard WebForm is generated with links to all converted Forms and Reports. For Crystal Reports, WebForms for viewing/printing reports and passing parameters are included.
- Strictly-typed VB.Net code is generated that performs all database interactions and form navigation.
- Test drive the Northwind ASP.Net demo.
| Convert MS Access Applications to Java |
|
- With the ASP.Net module, an accurate and consistent DB2 foundation is laid for Java client-side development.
- A number of third-party software companies offer ASP.net to Java converters, including Grasshopper 2.0
We offer purchase and lease options and modular pricing, which depends on the target DB2 platform (ex. x-series, z-series) and client-side framework. For pricing, please complete the Sales Inquiry form or phone us at (877) 356-9191.
|
Developer Guide