AND, also from my limited knowledge, SharePoint does not allow for MS Access to update the SharePoint List (I may be wrong on this, so I appreciate other experts jumping in on this one) unless the specific permissions are set for that user. And, your queries will behave differently in a List than with a Table.
I can easily link to Sharepoint lists; however, to be able to even read the list, the Sharepoint admin must allow my user profile read rights to that part of the site. The same is true if I would like to write data back to the site.
IMHO: Sharepoint is broken for database useage mainly for two reasons:
- It does not support the VBA commands. Only things that you can do from a MS-Access-MacroCommand (and even then very limited) can be called from your forms.
- Sharepoint does not support the relational links (AccessRibbon>D atabaseTools>Re lationships) You must use the nasty little lookup-field at the TABLE LEVEL to establish the workaround and these are sometimes a bit fickle as to if they will work or not work correctly with the Sharepoint site.
- FE/BE-Splits: Sometimes the slowness is because each user does not have their own copy of the FE on their client. Also tables that either seldom or do not change (say a table with the names of the weekdays, or USA State names and abreviations) should be pushed to the FE to be used at the client end.
- Another reason for the slowness can be if you have what I call a server-side installation of office... which was not the intent of MS Office.
timers going off and I need to get them going...
Comment