Updates to front-end and impact with SharePoint tables
Hi, I've developed a database and split it into a front-end and back-end databases. I then from the front-end exported the data to a SharePoint list. The reason for this is that there are three remote locations plus a main-office location for this application. It is my understanding that the front-end, (which grew in size after I exported the back-end tables to SharePoint), actually contains a copy of the tables that are now on SharePoint. If this is correct, my question is when I add functionality to the front-end or fix bugs and distribute a new front-end, the new front-ends tables will be out of sync with the tables in the SharePoint lists, so what happens. I think my hope is that the data from the SharePoint lists are downloaded to the new front-end copy of the tables vs. the new front-end, outdated tables overwriting/updating the SharePoint tables. In the past I always split the database and when I made changes to the front-end, since the tables were linked to the back-end, either on the same local machine or on a server shared folder, things worked great. In this case with SharePoint lists, I just don't have any experience, but I'm sure I'll learn.