![microsoft access 2013 redistributable vs database engine microsoft access 2013 redistributable vs database engine](https://hajarsabrani.com/wp-content/uploads/2017/08/115857-636216268232518694-16x9-1-1-1536x864.jpg)
In fact, if you have the full version of Access, you can open the app and modify tables, queries, and macros doing considerable damage. If you call the FE the "executable", you will begin to think of it as such (language is very powerful) and it is most certainly not an executable. Best to refer to the two files as FE (for the application objects) and BE (for the table objects). Second, if I am wrong, do you have any instructions or reading material that I need to look at to resolve my dilemma?Īs always, help is very much appreciated.Ĭlick to expand.Do not confuse the Access.
![microsoft access 2013 redistributable vs database engine microsoft access 2013 redistributable vs database engine](https://i.stack.imgur.com/SDGpf.png)
From our initial look at this, the ability to link the executable access file to the database file is only available with a developer version of Access.įirst question is am I correct in that I cannot link a split database that resides on different computers if i only have the runtime version installed? The problem seems to be that the site where the application is being stored will only be using the free runtime version of access rather than a developer version. My understanding is that when the user starts their executable, they can select/connect to the actual database files on the server using a configuration setting. This approach also allows new versions of the software to be passed out without impacting the actual database (unless the database structure itself is also being modified). The database file gets saved on a server and the executable get stored on the client workstations linked in the office network. Then the software version gets saved as an executable/compiled version so that end users cannot use or change the software. So, best practice is to split the database into software and database files. I have a database that will be placed in a multi-user environment. Hopefully, I will get my thoughts down correctly.