SharePoint List

[zezo2021]

Hello

Are there any disadvantages to using Share Point Online list as a backend Tables for Access

 

[GPGeorge]

Limitations on the number of records the SharePoint environment can be expected to handle efficiently is the main one, I think.

If your tables have fewer than around 25,000 to 35,000 records, SP might be okay. Some might argue for fewer than 20,000 as being optimal.

 

[theDBguy]

There are a few, but there are advantages as well.

 

[MajP]

No referential Integrity. You have to handle cascade updates, deletes, and enforce RI through your FE.

 

[zezo2021]

Is there a limit for users?
How many access front ends can access the list?

 

[GPGeorge]

No referential Integrity. You have to handle cascade updates, deletes, and enforce RI through your FE.

Not true, actually. At least not in the sense we normally think of with regard to enforcing relationships.

SharePoint lists use the ugly Lookup Fields to create and enforce "Relationship Behavior" between lists. This is essentially the same thing as a Lookup field in an Access table, as a matter of fact.

 

[theDBguy]

Is there a limit for users?
How many access front ends can access the list?

Don't know of a hard number, but probably about the same limit as when you use an Access FE to any other BE, including Access.

 

[GPGeorge]

Further to what theDBGuy said, I think there are probably "Published" limits, and then there are "Practical" limits on all things related to SharePoint. Circumstances, dictate what is going to be practical in YOUR situation as opposed to some theoretical standard.

This video is a pretty good overview of what you can and can't expect with Access/SharePoint.

Oops. I had grabbed the wrong URL.