| | SQL Server (ADP Project) Implementation Notes UI Builder has not yet been fully certified against Microsoft SQL Server as an ADP project. Because Access uses data types native to SQL Server. Please click here to request notification when UI Builder is certified against SQL Server using ADP/ADE projects. Please note that Microsoft recommends using MDB/ACCDB to connect to SQL Server as opposed to ADP projects. Refer to Microsoft TechNet for additional information. | | SQL Server (Linked Tables) Implementation Notes UI Builder has been certified against Microsoft SQL Server (with the limitations specified below). - Be sure to leave the following tables on your local Microsoft Access file: tblSubMenu_options, tblUpgrade
- Users must have authorization to write to tblAppInfo and tblAppInfo_advanced if they are allowed to administer settings.
- Be sure audit tables include a primary key field that does not exist in the source data table. Otherwise the table will not be updateable.
| | MySQL ServerImplementation Notes UI Builder has been certified against MySQL (with the limitations specified below). Be sure to leave the following tables on your local Microsoft Access file: tblSubMenu_options, tblUpgrade Users must have authorization to write to tblAppInfo and tblAppInfo_advanced if they are allowed to administer settings.
| |
| Known Limitations The Enterprise Edition auditing functionality will work correctly, however the setup wizard step (Step 1) to create an audit table will not function with SQL Server. You will need to create the audit table on the target server, and add the audit fields to the table manually. Refer to the Enterprise Edition guide for the list of fields. The upgrade feature built in to UI Builder will not function as UI Builder needs to create new tables in the database. You can upgrade UI Builder by manually importing forms and modules from the latest version released from OpenGate Software. The newest version's data in table tblSubMenu_options should replace the data in the same table on the SQL Server.
| | Resources Microsoft TechNet article on Microsoft 2007 Migration considerations |
| | Known Limitations The Enterprise Edition auditing functionality will work correctly, however the setup wizard step (Step 1) to create an audit table will not function with SQL Server. We recommend you create the table using the Audit setup Step 1 on your local database, then use the Access Upsizing Wizard to move the audit table to the SQL Server. The linked table verification and repair feature of UI Builder will not recognize or repair broken links to SQL Server.
| | Resources Microsoft resources on upsizing Access 2003 to SQL Server Microsoft resources on upsizing Access 2007 to SQL Server |
| | Known Limitations - The Enterprise Edition auditing functionality will work correctly, however the setup wizard step (Step 1) to create an audit table will not function with MySQL. We recommend you create the table using the Audit setup Step 1 on your local database, then move the audit table to the MySQL Server.
- The linked table verification and repair feature of UI Builder will not recognize or repair broken links to MySQL Server.
| | Resources MySQL Migration Toolkit Technical Guidance on Migrating to MySQL from MySQL AB |
| |
