• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 549
  • Last Modified:

Sharing an Access Database Over the Network

I have an Access database, split into a front end and backend, on a network share. Users access the database by navigating to the share and then the file. I have checked that all permissions are set accordingly on both the front end file and the backend file, as well as the parent directories. Some of my users are able to access the database and some are not, although they are all in the same security group that grants access to the share. The users who cannot access the database receive the following error:

Could not find the file 'Q:\blahblahblahblah\File.accdb' The file in question is the backend file.

I know this is just a simple path issue or something but I need some help...Any suggestions?
0
BoxunloX
Asked:
BoxunloX
  • 3
  • 3
  • 2
  • +4
3 Solutions
 
DoveTailsCommented:
First thing that came to mind ... we have some users who disconnect drives to improve file searching.  Could it be as simple as someone not have that drive letter mapped on their PC ?
0
 
BoxunloXAuthor Commented:
@DoveTails - Tried and tested. Still a no go.
0
 
Dale FyeCommented:
A couple of issues here:

1.  Every user should have their own version of the front end, installed on their own PC (no exceptions).

2.  linked tables should be liked using the full network path  \\Servername\folder1\subfolder\filename.accdb, not with a drive letter.  Unless you have this functionality locked down or automated, not all users will have the same drive letter associated with the same network path.

0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Agreed with fyed, and also:

You need to insure that all users have Full permissions on the folder hosting the backend database file. I realize you've said they're all in the same group, but carefully review the permissions of that folder.

0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
fyed,

<<2.  linked tables should be liked using the full network path  \\Servername\folder1\subfolder\filename.accdb, not with a drive letter. >>

 That need not be a given.  I've never used UNC naming for apps and have never had an issue yet.

<<You need to insure that all users have Full permissions on the folder hosting the backend database file. I realize you've said they're all in the same group, but carefully review the permissions of that folder.>>

  Don't forget there is Share Permissions and Directory Permissions...

JimD.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
If I understand correctly, the minimum permissions you can provide is Modify perms on the folder. This allows the user to read/write/create/destroy items in that folder, but restrict their ability to remove the folder (but I could be wrong).

0
 
Dale FyeCommented:
JD,

<<I've never used UNC naming ...>>

Really?  Are your users in an environment where everyone has the same network drive mappings?  Or do you just include a relinking functionality that allows users to relink on their own?  

I generally provide the latter, just in case someone renames the folder containing the backend, or in case they put it on another server.  I find that if you use a Auto Frontend Updater (of some sort), that using UNC naming is the safest way to make sure all users will have access to the backend.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<Really?  Are your users in an environment where everyone has the same network drive mappings?  Or do you just include a relinking functionality that allows users to relink on their own?  >>

  A mapping is created in a login script, so they all get the same.  I also have a test/verify of each BE DB at app startup.  If it fails, then can browse to the location.  If they cancel that, the app quits.

JimD.
0
 
clarkscottCommented:
Make sure your users have WRITE access to the folder as well as READ.  Access creates 'ldb' file to control sharing.  If the user doesn't have WRITE access... Access can't open the back-end.

Scott C
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Modify or Full permission would include read/write/create/destroy.
0
 
Armen Stein - Microsoft Access MVP since 2006Commented:
To confirm that it is a permission problem, have one of the users try to browse to the folder and open the BE directly.  This should tell you right away whether they can see and open the BE file.  Then follow the advice already given to ensure correct permissions.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<To confirm that it is a permission problem, have one of the users try to browse to the folder and open the BE directly.>>

  I usually this check:

1. Have them open explorer
2. Browse to the directory
3. Right click and do a new text file.
4. Double click on the text file, edit it by typing a few characters, and then save it.
5. Then right click and delete it.

  If they can do all those operations via the network share, then the permissions are correct.

JimD.
0
 
BoxunloXAuthor Commented:
You guys were absolutely correct. The issue was that the user had split the database using a relative path instead of an absolute one. Simple as that. I checked the paths to his tables within Access and they were all referencing relative locations. I had him re-split the database, referencing the absolute path to the file, and it worked beautifully.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 2
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now