Access network design: FE configuration

[Blings]

I have a database which has 8 concurrent users. I've configured it so that all frontend files are located on the SERVER folder as follows:

1. ARC CRM - Carmen
2. ARC CRM - David
3. ARC CRM - Despatch
4. ARC CRM - Greg
5. ARC CRM - Lucrezia
6. ARC CRM - Margaret
7. ARC CRM - Production
8. ARC CRM - Sarah

The backend files are:

1. RawData
2. RawDataSalesOrders
3. RawDataSuppliers

I understand that the FE file should rather be on the users` local machine instead of accessing their FE file from the server, I configured it that way because when I roll an update out I simply replace their file from the master which is "ARC CRM." When I do an update to the master file "ARC CRM" how can I push the update to each of the users` local folder e.g. C:\Database, conveniently?

[pbaldy]

Many of us use some sort of front end updater, where the user isn't actually starting the app, they're starting the updater. The updater can copy the file when appropriate and then start it. I create an exe with C# that examines a version table in the front end. There are many other ways. Simplest is a batch file that copies the front end every time and then runs it.

[Blings]

Wow. I cannot believe that I managed to pull this off, thank you for pointing me in the direction - I've managed to do it!

Solution:-

Location: "C:\Database" inside this folder is "Copy & Run ARC CRM.bat" which has the following code:-

xcopy "\\SERVER-FOLDER\Database\ARC CRM.accdb" "C:\Database\" /d
"C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE" "C:\Database\ARC CRM.accdb"

I've then placed a shortcut on the users desktop and changed the icon.

[pbaldy]

Good job!!

[Welshgasman]

You should be supplying accde not accdb files?

[Blings]

You should be supplying accde not accdb files?

Could the error be because I have "modern charts" in my report form section of the dB?

[CJ_London]

the first error will be because you have code that won't compile. You should have option explicit at the top of every module and the code compiled. Do this and resolve all errors then try again.

the second message is just a warning. providing your users are using the same or later version than there will not be a problem. As a developer you should be developing using the earliest version your user base has available.

You may also need to develop with the assumption that a user does not have access installed and will use runtime. Be aware that if a user installs runtime and they already have (or subsequently install) a different version of access this can cause issues.

Runtime has many features disabled - the most apparent being the navigation window, the ribbon and right click menu shortcuts. If your app relies on using these features, you will need to write your own. It also doesn't take kindly to errors - if one is encountered, the user won't get any sort of helpful error message, just something along the lines of 'encountered an error and the app will close'. So your error handling needs to be up to scratch as well.

You can test your app as if in runtime by changing the file type from .accde to .accdr and then open it.