Microsoft Access 2010 Bible

Chapter 35: Deploying Access Applications to SharePoint

1151

FIGURE 35.8

The products table as a SharePoint list

If an export error occurs, Access creates a new table named Move to SharePoint Site Issues that

contains a row for each export error. The information in the Move to SharePoint Site Issues table

tells you which field in which table failed to export, and why. The table does not suggest how to

correct the issue, but in most cases a simple export such as this fails because of data or name

incompatibilities between Access and SharePoint. Very often, changing the name of a field (as in

this example) is enough to allow the export to proceed.

In spite of the apparent success of the export process just described, several issues were recorded

in the Move to SharePoint Site Issues table (see Figure 35.9). None of these issues were fatal to the

export process, and all issues may be resolved on the Access side, if necessary.

For instance, one reported issue is that the Picture_Small field was not exported to SharePoint.

Because the pictures are important to the users, it would be helpful to come up with a solution.

One approach is to set up an Access table that contains only a product ID and the corresponding

product picture. You then use a query to join the picture table to the linked products table so that

forms and reports still receive the Picture_Small field and display it the same as before the

export. Because tblProducts is now a linked table, it’s not possible to create a formal one-to-

one relationship between tblProducts and tblProductPictures, but Access easily handles

an ad-hoc join between tables in a query.