|
Convert MS Access Databases to MS SQL Server ™
and Applications to Client/Server, ASP.Net
Scriptoria for SQL Server™ 2000/2005 is an Enterprise quality database migration and application conversion toolset for Microsoft Access.
|
 |
Scriptoria for SQL Server™ Features |
| Data Model Conversion |
|
-
All Access data types, including AutoNumber and OLE Objects are supported.
Equivalent SQL Server data types can be assigned to individual columns (ex. varchar
for one column and CHAR for another).
-
MS Access Memo types, which default to SQL Server 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.
-
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.
-
Design flaws, like redundant indexes and unnecessary cascade update constraints are
detected and optionally corrected.
-
Access Validation Rules that specify user-defined Validation Text
messages are implemented using triggers.
-
Foreign-Keys 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 SQL Server indexes are created; duplicate Access index definitions are
ignored. All MS-SQL index options, like CLUSTERED and Fill Factor, are definable
-
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.
-
SQL Server File Groups are optionally assigned to tables and text/image types.
-
Conversion warnings and errors are logged in an Access table for later review.
| Export MS Access Data to SQL Server™ |
|
-
Data can be loaded without recreating table definitions.
-
To obviate load errors, foreign key constraint checking is deferred until all data is loaded.
| Convert MS Access Query Definitions to MS SQL Server |
|
- All Microsoft Access Query Definitions are translated into SQL Server T-SQL views and/or stored 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 SQL Server functions or user-defined functions (SQL 2005 only) we provide.
- Sub-queries are implemented using SQL Server derived tables.
- SQL Server views and procedures are automatically recompiled when MSAccess/SQL Server table structures are changed.
- 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 SQL Server 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.
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