Migrating Legacy Database to SharePoint Web Tables - Whitepaper

Here’re the steps you can follow before you can publish your application to Access Services: Save your application in default database format (.accdb); Run Compatibility Checker to see if your app’s schema is web compatible; Open Web Compatibility Issues Table. The errors in table are explanatory with which table, which control you’ve and there’s also […]

Here’re the steps you can follow before you can publish your application to Access Services: Save your application in default database format (.accdb); Run Compatibility Checker to see if your app’s schema is web compatible; Open Web Compatibility Issues Table. The errors in table are explanatory with which table, which control you’ve and there’s also a link for each error where you can also get info about what to do; Fix errors in Web Compatibility Issues Table and run Compatibility Checker until your appl is Web compatible. Now your data is web compatible and you can publish it to Access Services. However, you can’t open your objects (Forms/Reports/Reports/Modules) other than tables in the browser since they are still client objects. There’s a pretty good white paper that talks about integration of Access Applications with Access Services. Before starting your schema changes, take a look at the “Migrating Legacy Data to Web Tables” section to see a list of common compatibility issues and their solutions. Knowing the schema changes you are expecting will definitely help you make right design changes in your application.

Download: Migrating Legacy Data to Web Tables (white paper)