Forum Discussion
MS Access
dajohnson162000hot Sorry, I forgot to address that portion of your query.
Each time you create a new version of the Front End accdb (or the compiled version accde) you will have to distribute that new FE to each user.
One way to think about this is to put it into the context of all relational database applications.
They have a data layer, which consists of the tables holding the data. In Access, that can be local Access tables, but it can also be any one of a large number of data storage tools, including the SharePoint lists. In other relational database application, the same is also true. A web page, for example, can work with data in SQL Azure or SQL Server, MySql, and so on.
They have an interface layer, which consists of forms in Access, or web pages in a browser-based application.
They have a logic layer, which consists of the code that manipulates both data and objects.
In the Access version, the FE accdb (or accde) is the interface layer. Access can connect to a data layer which is another accdb, a SQL Server database, or, in this case, SharePoint lists, and so on.
What you are doing, is in essence, putting the interface, or FE, on a SharePoint site for deployment to each user. The SharePoint lists are separate, i.e. they are part of the data layer.
- dajohnson162000hotJun 08, 2020Copper ContributorGeorge, Thanks so much! Yes, I was suspecting what you have stated to be the case. If I run queries to pull data--no worries. The FE is a fixed object that when I change I just need to republish the updated version to the users machines. Got it! If it's ok I would like to stay in touch with you if I happen to encounter any problems. Thanks! David