1123csh
Aug 13 2010, 10:02 AM
Since Microsofts latest updates multiple users can no longer open the same Access file at the same time. Does anyone have any idea how to fix this issue.
Thanks in advance.
MiltonPurdy
Aug 13 2010, 10:05 AM
Is your database split into BE and FE? You don't generally want users working on the same record at the same time, you will get conflicts. Check tool/options/advanced at see what you settings are. You should be on shared.
Jeff B.
Aug 13 2010, 10:06 AM
I've not (?yet) run across that issue.
Could you describe your setup a bit more? For example ...
?what version
?Front-end/back-end
?Front-end on each PC, one back-end on LAN
More info, please...
Alan_G
Aug 13 2010, 10:07 AM
Hi
Is your database split into a front end and back end set up, with each user having their own copy of the front end on their local workstation linked to a backend located in a shared place ?
1123csh
Aug 13 2010, 10:15 AM
Thank for all the replies!
Our database is on a shared file server both the front end and back end .
I checked the settings and the database is setup to be shared.
let me know what else you need thanks again!
Jeff B.
Aug 13 2010, 10:18 AM
If both FE & BE are on the same server, then every user is "hitting" the (single copy of the) front-end at the same time.
This causes significant network traffic (the network police will track you down!), and greatly increases the risk of corruption.
The preferred design is to put a copy of the front-end on EACH user's PC, linked to the (single copy of the ) back-end on the server.
Good luck!
1123csh
Aug 13 2010, 10:38 AM
Thanks Jeff!
I was pretty sure that it needed to be done like that but this is the way we have done it for a long time and havnt had to many issues with it. Although I would like to make the changes so that its correct in the future.
As far as the issue with us not being able to open the database at the same time, I dont believe that the front end set up would be the cause of that because we have always been able to perform this operation up until this last Microsoft update.
One thing we have found that does work is if I have the database open and then go to another PC and open Access and browse for the file and open it from there it will open. But this is the only way.
Thank you,
Shane
MiltonPurdy
Aug 13 2010, 10:53 AM
Also, I would compact and repair the BE and FE. And make sure the users have read/write/edit/delete rights to each file AND the folder they reside in.
KingOSlots
Aug 13 2010, 01:34 PM
we ran into this same situation after Office 2007 was installed on Vista machines. Our solution was to put shortcuts on each user's desktop pointing to the applicable database, but adding the path to the Microsoft Access executible ("C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE") and then the actual database file, in the target section.
Alan_G
Aug 13 2010, 03:11 PM
Hi KingOSlots
Welcome to UtterAccess

When you say
QUOTE
Our solution was to put shortcuts on each user's desktop pointing to the applicable database
I'm not sure whether you mean pointing to a shared single copy, or each user has their own copy of the front end installed on their own PC. If it's the former method (one shared file), just so you know, that's
not the recommended way of doing it and is one of the sure ways of leading to corruption sooner rather than later.
If either you or 123csh have been getting away with it, then for my money you've been lucky so far. Each user should (I was going to say must, but that's not strictly true) have their own copy of the front end on their own local workstation linked to a single back end in a shared location.
There's nothing to stop you doing it the way of course, it's your application and obviously you're free to do whatever you want with it, just trying to point out the pitfalls
1123csh
Aug 16 2010, 12:29 PM
Thank you Alan_G, KingOSlots and Milton Purdy.
What I did to correct the problem is I Took the front end and saved a copy on each users personal computer and kept the single back end workstation on the shared file. The front end on each single personal computer is linked to the shared back end.
This seems to work fine expect I wish it was possible to have multiple users create a new record at the same time which I'm pretty certain you cannot do.
Thanks for everyones help! This is a great sight!
Jeff B.
Aug 16 2010, 01:21 PM
Why are you suspecting that you can't have, say, 10 users each adding a new record simultaneously? Have you tried that? If so, what happens to give you that impression?
1123csh
Aug 16 2010, 01:57 PM
Thanks Jeff B.
Well lets say if I'm entering a new record and so is someone else at the same time. If I finish mine first then the other person cannot save theirs.
Now if we want to update two different records that all ready exists at the same time we can do that.
Shane
jamesfred
Aug 16 2010, 02:30 PM
Shane,
Pardon my jumping in but I wanted to point out a mistake that was made where I work. We had split the BE/FE and put the FE on the C: drive of those who needed it. The developer maintained the FE and periodically made modifications to it. Unfortunately users were not getting the same information in the same manner as could be gotten from the developer's FE. He forgot to put the modified FE out on the shared drive and notify all users to copy it onto their C: drive. But this may not need to be said to this august body of people. I'm not sure this developer is a subscriber to this great site.
Best wishes as you continue your project.
1123csh
Aug 17 2010, 07:29 AM
Thanks Jamesfred
No! I appreciate your input and thanks for trying to help. I am aware of the issues that you are referencing and try to be very careful in my all my updates to font ends. Thanks for the advice though.
Shane
1123csh
Aug 17 2010, 07:35 AM
Jeff B.
We only have two users trying to input data at the same so I've tried more than one user but never as many as ten. The problem is if we are creating a new record that is a part of the same table. I can't get Access to add two new records in that table at the same time. I have always thought that was something that Access just couldn't do. Hopefully I'm wrong!
Thanks Again!
Shane
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.