 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / November 2007Local area network permissions and Access databases - Desperate
Hello I am a bit desperate here, so any comments are most welcome as this is a bit of an open question, and I may need to contract an expert. I have built an Access database which I copied to a shared drive on my company's local area network. I then split the database and detached copies of the front-end to each user's desktop. I then asked the Lan administrators to remove the delete permission from all bar me as I did not want anyone deleting the back-end database. After successfully testing this with a few users I found that some could not update the database with new records. I am sure there is nothing wrong with the database itself I think there is some issue with the Lan setup. What could these be? Again, If some of you do freelance work please respond as we may require your services Many thanks Nick Hi, Nick. > I then asked the Lan administrators to remove the delete permission from > all > bar me as I did not want anyone deleting the back-end database. It's much better to put the database file in a hidden shared directory on the network. If users can't see the file, they have a fairly difficult time deleting it. > I am sure there is nothing wrong with the database itself I think there is > some issue with the Lan setup. What could these be? Not all of the users have write or modify permissions on the directory, so they can't make data edits. And some of them with a lack of permissions will prevent others from even opening the database -- even those with Full Control. > Again, If some of you do freelance work please respond as we may require > your services You don't need to hire a consultant. Have each database user try to create a new text file with Notepad in that directory, then close the file. Then open the file and modify it by adding some text and try to save the file. After it's saved, try to delete the file. If all database users cannot perform all four of these operations successfully, then the Microsoft Access database files stored in that directory cannot be used the way they were designed. It's best to give Full Control Windows security permissions on the directory to avoid the problems you are encountering, but when Windows System Administrators try to give less than Full Control, at least 95% of them get some of the permissions wrong on the first try when there are more than a dozen users to assign permissions to. HTH. Gunny See http://www.QBuilt.com for all your database needs. See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials. Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info. > It's much better to put the database file in a hidden shared directory on > the network. If users can't see the file, they have a fairly difficult > time deleting it. Hi Gunny, I've heard this quite often but how do you actually go about it on a corporate server if you're not an administrator? Do you mean to just check the "hidden" box in the properties? In which case it just needs the malicious user to show hidden files ... what am I missing here? Regards, Keith. >> It's much better to put the database file in a hidden shared directory on >> the network. If users can't see the file, they have a fairly difficult [quoted text clipped - 6 lines] > check the "hidden" box in the properties? In which case it just needs the > malicious user to show hidden files ... what am I missing here? Remember that Gunny said "shared directory". It's as simple as putting a dollar sign at the end of the share name when creating it.  SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) > Remember that Gunny said "shared directory". It's as simple as putting a > dollar sign at the end of the share name when creating it. Thanks Doug. So all this must be done from a DOS prompt? Keith. No. You create a share, and add a dollarsign to the end of the name: SecretBackends$ The front-ends then connect to the backend at: \\someserver\SecretBackends$\some.mdb Note: a shared folder is not the same as a mapped drive. -Tom. >> Remember that Gunny said "shared directory". It's as simple as putting a >> dollar sign at the end of the share name when creating it. > >Thanks Doug. So all this must be done from a DOS prompt? > >Keith. > Remember that Gunny said "shared directory". It's as simple as putting a > dollar sign at the end of the share name when creating it. It would seem that you need admin rights to your PC in order to do this, something I don't have at my place of work. Keith. No, but if you have a need, surely your IT boys and girls can provide those rights.Sometimes you simply have to ask. SignatureThe personal opinion of Gary G. Little >> Remember that Gunny said "shared directory". It's as simple as putting a >> dollar sign at the end of the share name when creating it. [quoted text clipped - 3 lines] > > Keith. > No, but if you have a need, surely your IT boys and girls can provide > those rights.Sometimes you simply have to ask. Unfortunately, the mere mention of the phrase "MS Access" sends them into a blind panic since we should not be using such a silly little toy that falls over every two minutes in our industry, we should be using the supported Oracle service for every little morsel of data we have to process. Oh, and they can charge us for the Oracle service too which might help colour their view ;-) Here's another newbie question though ... if I *did* get IT to set up a hidden share, how would I, as a non-admin, see it? Keith. Let them be the testers, and find out how stable it is/isn't. You can't see it, but you know it's there and you can use it: \\someserver\SecretBackends$\some.mdb -Tom. >> No, but if you have a need, surely your IT boys and girls can provide >> those rights.Sometimes you simply have to ask. [quoted text clipped - 10 lines] > >Keith. > Let them be the testers, and find out how stable it is/isn't. I'm happy to say that all of my apps are stable but our organisation lets anyone loose on Access with obvious consequences. Every time I'm asked to "help with an Access db that somone "developed" but has moved on" I'm confronted by a number of unrelated data tables with redundant data so I have to start again. > You can't see it, but you know it's there and you can use it: > \\someserver\SecretBackends$\some.mdb Understood, thanks Tom. Keith. I have just realised that the problem is that some users have a different network path to the folder than I do. Could this be the problem and if so is there a way of changing the database so that it can be accessed from any path? I really appreciate your comments Many thanks again and kind regards, Nick > > Let them be the testers, and find out how stable it is/isn't. > [quoted text clipped - 10 lines] > > Keith. Not sure I understand what you mean by "accessed from any path". The database can only have one location. You can refer to that location using a UNC \\server\share\folder\file.mdb or you can map a drive to \\server\share and then refer to that location using the drive letter, like F:\folder\file.mdb. If different people have different mapped drives, you'll have problems, but if you use the UNC, it doesn't matter how their drives are mapped (or even if that particular share is mapped) SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) >I have just realised that the problem is that some users have a different > network path to the folder than I do. [quoted text clipped - 22 lines] >> >> Keith. > ... Every time I'm asked to "help with an Access > db that somone "developed" but has moved on" I'm > confronted by a number of unrelated data tables > with redundant data so I have to start again. That's not at all unusual. I've found it to be the rule rather than the exception. I often had this mental picture of a developer running off, screaming, into the night just to get away from the monster she/he'd created. Larry Linson Microsoft Access MVP |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.