Microsoft Access 2010 Bible

Part V: Access and Windows SharePoint Services

1152

FIGURE 35.9

The final export issues list

An alternate approach, and one that must be completed before exporting the tables to SharePoint,

is to add an Attachment field to tblProducts and use it to store the product pictures. Oddly

enough, Attachment fields export to SharePoint without a problem, so the picture can be seen both

in SharePoint and in Access. This solution requires changing the queries, forms, and reports in the

Access application to use the new Attachment field instead of the former Small_Picture field.

In spite of the errors shown in Figure 35.9, the Access application continues to function as before.

During the export process, proxy fields are added to the SharePoint lists as placeholders for the

fields that cannot be exported to SharePoint. These fields are typed as “Single line of text” in

SharePoint and allow the Access queries, forms, and reports to function as before, even though no

data is shown in bound controls on the forms and reports. In this example, you have to devise a

solution for the missing SharePoint data before users are able to see the product pictures.

Keep in mind, however, that if you change the name of a field or make other changes to an Access

table during the export process, you will have to correct your queries, forms, reports, VBA code,

and other database objects. If you make changes, test the application before proceeding with the

export because you will have less control over the table’s design after the export is complete.