|
Convert MS Access Databases to Oracle ™
and Access Applications to Client/Server, ASP.Net, Java
Scriptoria for Oracle™ is an Enterprise quality database migration and application conversion toolset for Microsoft Access that embodies many years of MS Access and Oracle expert knowledge.
|
 |
Scriptoria for Oracle™ Features |
| Data Model Conversion |
|
-
Access names are automatically renamed to conform to Oracle naming rules. Assigned
names may be replaced by any valid Oracle name.
-
Object naming conventions that conform to your DBA standards can be applied to all generated objects. For example, triggers may be prefixed and or suffixed with user-defined identifiers; ACCT_CUSTMERS_USA1, where ACCT is the prefix, CUSTOMERS the table name, USA is the suffix and "1" is an auto generated value to ensure uniqueness.
-
All Access data types, including AutoNumber and OLE Objects are supported.
Equivalent Oracle data types can be assigned to individual columns (ex. VARCHAR2
for one column and CHAR for another).
-
MS Access Memo types, which default to Oracle LOBs, 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.
-
Design flaws, like redundant indexes and unnecessary cascade update constraints are
detected and optionally corrected.
-
Access Validation Rules are converted to Oracle CHECK constraints or triggers when
appropriate. Validation Rules that specify user-defined Validation Text
messages are implemented using triggers.
-
Access Default Values that do not conform to Oracle rules for specifying defaults
are converted to Oracle 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 unique indexes are created as specified by
the Access design.
-
Equivalent Oracle indexes are created; duplicate Access index definitions are
ignored.
-
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.
-
Oracle table spaces are optionally assigned to tables and LOBS.
-
Conversion warnings and errors are logged in an Access table for later review.
| Export MS Access Data to Oracle™ |
|
-
Data extracted from Access tables is converted to Oracle SQL*Loader compatible
files.
-
Oracle table data can be migrated using a generated Oracle script or from within
Scriptoria.
-
Data can be loaded without recreating table definitions.
-
To obviate load errors, foreign key constraint checking is deferred until all data is loaded.
-
Sequence Start values are reset to reflect current Access Auto Number values.
-
Displays complete Oracle import/load log information
-
Load time is minimized for MS Access tables containing Memo and OLE Object data.
| Convert MS Access Query Definitions to Oracle™ |
|
- All Microsoft Access Query Definitions are translated into Oracle PL*SQL 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 Oracle functions or user-defined functions we provide.
- Sub-queries are implemented using Oracle derived tables.
- The generated procedures can be combined into a single
Oracle package.
- Oracle views and procedures are automatically recompiled when MSAccess/Oracle 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 Oracle 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 Oracle 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 selected client-side framework. For pricing, please complete the Sales Inquiry form or phone us at (877) 356-9191.
|
Developer Guide
Scriptoria vs. Oracle Migration Workbench