[AccessD] Access and Sharepoint

[Jim Dettman]

<<I have not read much detail about this but what I have read
indicates that unless he database is very basic then the Access/Sharepoint
combination falls short.
>>

 There are two approaches here in regards to SharePoint:

1. Desktop DB storing data in SharePoint

2. A Web database or web app.

For #1,  data is stored in SharePoint lists, which after 5,000 records
perform quite poorly.   SharePoint is not a relational DBMS.   You'd be far
better off with a SQL server BE.   I'm not sure why anyone would even
consider using this approach.

For #2, with Access 2007/2010 data is in SharePoint.   So besides data
performance problems, you also have a FE that is not all that flexible.
Good for basic CRUD operations and that's about it.

 With Access 2013/2016 - Data for Web Apps is stored in a SQL Server
BE....much better.   SharePoint is still involved as it hosts the FE, but
your still stuck with a limited FE.

Jim. 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
David Emerson
Sent: Friday, November 04, 2016 05:32 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access and Sharepoint

Hi Team,

 

I have a potential client that is talking about using Sharepoint with an
Access FE.  I have not read much detail about this but what I have read
indicates that unless he database is very basic then the Access/Sharepoint
combination falls short.

 

The client doesn't need internet access to the database - it could be run on
their internal network.  I haven't yet been given a description of their
requirements so not sure how complicated the project may be in regards to
table structure and data size.

 

Any thoughts or helpful links?

 

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

 

 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com