1 / 18

MUST Pack And Go Migration Demonstration

MUST Pack And Go Migration Demonstration. Upsizing an Access back-end and re-linking an Access front-end database to SQL Server. Put your application files in a directory. You also need the MUST2000Data.mdb file (for all versions of Access), and MUST2000.mde, MUST2003.mde or MUST2007.accde.

hua
Download Presentation

MUST Pack And Go Migration Demonstration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MUST Pack And Go MigrationDemonstration Upsizing an Access back-end and re-linking an Access front-end database to SQL Server

  2. Put your application files in a directory. You also need the MUST2000Data.mdb file (for all versions of Access), and MUST2000.mde, MUST2003.mde or MUST2007.accde. The 2 MUST files need to be in the same folder as each other. Double-click the MUST2000.mde or MUST2007.mde or MUST2007.accde.

  3. Select the Pack And Go (Easy Start) Menu.

  4. Start at step 1.

  5. Our example back-end database only contains data.

  6. If you are using SQL Server 2000, then make the appropriate selection to MAP Access data types to SQL Server data types. Give your database a system name “NWData” and enter the full file path to the database.

  7. Press button 2 to link to the database.

  8. Press button 3 to Analyse the database and allow you to correct for errors. Press OK and you will move to the next stage, resolving any errors.

  9. This button is used to resolve serious errors, but we do not have any here. This button resolves less serious errors such as inefficient indexing. Press this button.

  10. The change log shows other changes made to the database mapping. A reporting menu can also be displayed.

  11. Press button 5 to generate the SQL Server Script files.

  12. Select the database using the drop down menu. Change to set a different name for the target database name on the SQL Server. Press the button to build the pre-migration script.

  13. This file assumes that you have created the target database, and can be run on SQL Server to create the table structures.

  14. Specify the file path where SQL Server will look for the Access databases. Then build the data import script. Also read the notes on enabling this in SQL Server. NOTE This is only available for SQL Server 2005, not 2000.

  15. The script also generates and populates a progress log. Data is imported from Access, it is also possible to directly import from secured databases; with appropriate settings in the windows registry.

  16. The final step creates the third file for adding relationships and checks.

  17. Run this script file to add relationships, indexes, Triggers and checks.

  18. This completes the demonstration, the DIRECT Menu presentation has details of how to complete steps 6 and 7 to re-link a front-end application. THANK YOU FOR YOUR TIME.

More Related