By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,327 Members | 1,797 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,327 IT Pros & Developers. It's quick & easy.

Problem with shared access program

P: 27
I have a shared access program is a shared directory on a server. I have put no restictions are set up anything different than the defaults. Some indivduals are not having any problem at all and love the input/output of the data. However, some indivduals click on the location and the file comes to their desktop as a 'read-only' file. Another indivdual will click on an item in the switchboard and they will do a back up of the database. Does anyone have an ideal why this is happening? It works great for about 90% of the individuals. Please help.

Randy
Dec 6 '07 #1
Share this Question
Share on Google+
4 Replies


Rabbit
Expert Mod 10K+
P: 12,392
For the read-only problem I would check the user's permissions on active directory or workgroup, whichever you use.

For the backup problem... I'm confused. Are you saying that no matter what button they click on the switchboard, it makes a backup of the database?
Dec 10 '07 #2

missinglinq
Expert 2.5K+
P: 3,532
Multiple-users with an Access app on a shared directory is, according to many, one of the leading causes of corruption, which may explain the strange Case of the Unwanted Backup!

Linq ;0)>
Dec 10 '07 #3

tdw
100+
P: 206
tdw
Multiple-users with an Access app on a shared directory is, according to many, one of the leading causes of corruption, which may explain the strange Case of the Unwanted Backup!

Linq ;0)>
Agreed. That was exactly why our VERY important orders database corrupted itself a few times, which caused us major headaches.

Finally, when I took over maintaining it, and decided to beef it up, One of the first things I did was to split it into a Front-End/Back-End database. That seems to have fixed that problem, and it runs much faster on user's computers.
Feb 6 '08 #4

MMcCarthy
Expert Mod 10K+
P: 14,534
I agree with missinglinq and tdw. Splitting the db to a frontend/backend is a good idea. And creating separate frontends for each user will make it even more efficient.

However, to direct back to your original question I think the issue is related to the fact that setting the database to shared is application specific. So if all your users have their own access application on their desktop you will need to check the settings in Tools - Options - Advanced and make sure they are all set to shared.

I do recommend though that you go with tdw and missinglinqs suggestion.
Feb 7 '08 #5

Post your reply

Sign in to post your reply or Sign up for a free account.