Split Access Db deployment

When you split an access database to accommodate say, 10 users, why do people recommend that you should only let your users work on a deployed client side front end? What happens if people use one instance of the front end on a network? On the Microsoft support website they include one network location as an option:
https://support.office.com/en-us/article/Split-an-Access-database-3015ad18-a3a1-4e9c-a7f3-51b1d73498cc

Do one of the following:
...Save the front-end database file to a network location that all database users can access, and then send your users an e-mail message that specifies the network location together with any other instructions they might need in order to access the database.]
RonBudget AnalystAsked:
Who is Participating?
 
Dale FyeCommented:
Generally, if multiple users use the same front-end on the server, it significantly increases the possibility of corruption of both that file, and your BE data.

The point of putting the FE on the server is to have it somewhere that your users can go to to get the latest version.  Most developers have a script or application that handles the process of updating the local users computer.

Some people simple use a batch file which delete the front-end on the users computer, copies the version from the server to the users computer, then starts the front end.

Others use some technique to compare the version that is on the users computer with the version that is on the server and only perform the delete and copy operations when the version changes.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<< why do people recommend that you should only let your users work on a deployed client side front end? >>

1.  As Dale said, it reduces the chance of corruption

2.  Performance wise it's better, as only data is going over the network.

3. It creates less problems in that you can use temp tables without needing extra steps if all the same users were using the same DB.

4. Although it's not recommended, there are some changes considered "Design changes" that can be done on the fly.  Since A2000, a user needs exclusive access to a file in order to make changes such as those.

Jim.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"On the Microsoft support website they include one network location as an option: "
Unfortunately, Microsoft recommends many things are are far from "industry standard best practices" ... and this is certainly one of them, the first reason being what Dale mentioned - corruption.  If a given user has a network glitch, then there is a good probability that the FE - in use by everyone - could become corrupted, bringing down everyone.  If each user has a separate copy of the FE on their workstation (best practice) ... this paradigm is greatly minimized.

mx
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Unfortunately, Microsoft recommends many things are are far from "industry standard best practices" ... >>

 LOL as we all know....just look at some of those sample apps<g>

Jim.
0
 
PatHartmanCommented:
The reference you are quoting is not a recommendation to use a single copy of the FE, please read it again.  It is telling you how to deploy a FE that links to SharePoint tables.  Generally, when you are using SharePoint, you use SharePoint to also distribute the FE, THAT is the central location they are talking about.  The recommendation is to not distribute databases that are linked to SharePoint lists because of the security info that is stored in plain text in the MSysObjects table.  Instead, they want you to put the database somewhere on the SharePoint site where everyone can download it and then separately send them the necessary SharePoint credentials to link the tables.
0
 
RonBudget AnalystAuthor Commented:
So I have users in multiple locations with different letter mappings to the shared drive. It appears that Network Discovery is disabled because I can't navigate through the Network to find the UNC server path. So...what will users with other drive mappings see? Will I need to ask them to re-link/refresh the table links to remap their FE's?

I tried a vba routine that changes the "Database = [path]" string  in the linked tables but got an error that the database was In State, but I successfully installed the Package Solution from the control panel and by Jove, it worked! I created the msi file and installed the application on my machine.
0
 
PatHartmanCommented:
If you can't "see" the UNC path, then ask your support people what it is.  You don't want to allow people to relink.  It is too dangerous.  Once they tell you the UNC path, use that so that everyone has the same link.  There is not even a reason to map a drive once you use UNC so it makes the BE a little safer since the users never see it in a folder.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Noting also that a give user's mapped drive letter (yours for example) may not be the same letter as other users ... oops ! ALWAYS ... user the FULL UNC Path to the Folder containing the back end db.  \\SomeDomain\SomePath .....
0
 
RonBudget AnalystAuthor Commented:
Thanks very much for your responses...

Where does one enter the UNC path? The splitter wizard and the linked table manager only allow me to browse folders...
0
 
RonBudget AnalystAuthor Commented:
Because I know the domain name, and if I looked at my Mapped Network Drives I can see the UNC Path, but I don't know how to link the tables using it
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Copy the UNC Path to the Clipboard.
Run the LTM.
Be SURE to check "Always prompt for new location"
Select your tables (probably All)
Click OK
When the File Dialog appears, paste the folder (UNC) path into the File name box and click 'Open'.
This should get you directly to the folder with your BE db.
Then select your db and click Open (again) .... and the relinking will execute.

mx
0
 
RonBudget AnalystAuthor Commented:
Thank you all for your high quality, generous responses!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.