I may have some difficulty explaining this. We are creating a SharePoint site to house an inventory. We will need read access to everyone and edit privs for a few. Currently, I have the data in an Excel file in a quasi relational setup. (I share a primary key across tabs). I am trying to determine the best approach based on:
- End users are competent in Excel, but unfamiliar with Access and need to perform updates before a front end is built.
- We are using Office 2010 but upgrading to Office 2016. Access isn't a part of the suite. I do not know about the SharePoint 2010 being upgraded to Office 365 or whatever. Nor do I know whether infopath will continue to be supported.
- They want to use Infopath forms as the method of updating records.
- Users are worldwide with firewalls and VLANS. I am not sure if this is relevant to the initial design.
- I suppose I want to design this in SP2010 knowing eventually Sharepoint will be upgraded and don't want to reverse engineer it if possible.
- There aren't a lot of records up upwards of 300 fields. (I can split them into relational tables, but with Sharepoint lists, I don't know about different sources.
- Part of me says Excel would be more user-friendly, but Access more efficient although Microsoft seems to be moving away from Access