TS, Execs and Splits! I need clarification please

[lmsm76]

I have a Access 2010 database (.accdb) almost ready and it will be used simultaneous for internal users and external users. External users means people outside from the company. My doubt is what's the best implementation for this.
For sure I need a Server with TS for the external users, but for the internal users can I take another approach?
Should I split the Database, and make a Executable file for the Front End?
It's not difficult to understand how to Split a Database, Create a Executable file and so on, but mixing all this starts to confuse me! Whats the best solution?

 

[Pat Hartman]

ALWAYS split multi-user databases. The FE needs to be distributed to each user and will be linked to the shared BE stored on a server. Make sure the people who set up TS/Citrix understand this since they will try to have everyone share a single copy of the FE (not good).

There is no such thing as an executable file when it comes to Access. VBA is an interpreted language unlike VB which is actually compiled. The Access database is a container type file. It contains code and data and because it contains data it can't be an .exe. Executable files cannot change and database files must change. The best you can do is to create an .mde/.accde which is compiled to p-code which will be processed by the interpreter.

Start by splitting the database (make a backup first). Once you split the database, move the BE to the server drive.
Second step - You will now need to relink the FE to the BE because the BE is no longer located at the path where it was when you split the db.
Third step - create the .mde/.accde from the FE (don't forget to backup first. It is IMPERARIVE that you keep the .mdb/.accdb in a safe place because you will need to go back to it should the FE require changes.)
Fourth step - distribute the FE

When you need to make FE changes, work on the saved .mdb/.accdb. When you're done, create a new .mde/.accde and distribute it.

 

[lmsm76]

It starts to be more clear now, but some doubts still remain.

The BE on the server it will be in a shared folder or it's not necessary?

The FE for the users in the internal network it's easy, each user will have their FE copy on their computer. Clear.

What about the users that will connect by Terminal Service? The FE for this users it will be the same? Or all this will be Managed by RemoteApp and the FE will be saved on each user profile on server?

When I spoke about ".exe" I was talking about supporting users without Microsoft Access. In this case the FE can be distributed by using the free runtime version of Access, meaning that the ".accdbe" will be converted to another format, right?

Many thanks!

 

[Pat Hartman]

The BE must be in a SHARED folder or people won't be able to share it.
Everyone needs a personal copy of the FE even the TS/Citrix people. Make your tech support understand that. TS/Citrix users should NOT share a single copy of the app.

The Access runtime engine can be downloaded for free from the MS download site. It doesn't alter the FE in any way. The runtime engine hides all access to objects so it is not possible to go into design view for anything even if your database is an .accdb. This doesn't secure your app in any way since anyone with the full version of Access can get to the design view. When you use the RTE, you MUST set your app to open to a form and give the user navigation options to get to other forms or perform specific tasks like export to Exce. The user will have only what YOU create for him since all the standard ribbons will be gone. You can create custom ribbons if necessary or just use forms to control everything. You may have to add a ribbon to allow printing since the user will not even have that unless you give it to him.

To test what your app woould behave like under the control of the RTE, change the extension from .accde or .accdb to .accdr. The .accdr extension tells Access to open this file in runtime "mode". This is also not security but it can deter some users who are not aware of the feature. You will need to change the extension back to .accdb to go into design mode on anything.