Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

cant open Access 2000 .mdb from win7 unless all other users offline

70 views
Skip to first unread message

oyster

unread,
May 8, 2010, 11:24:40 AM5/8/10
to
I have a simple single(not split) Access 200 .mdb in a shared folder used by
3 users all running XP.
Recently added a Window7 pc and loaded Office2kpro but was unable to update
through office update I guess because 'no longer supported'
It works fine but only if the Win7 user is the first to open the .mdb and
create the .ldb. Then all users can use as normal. But if an xp user has
opened first and an .ldb exists then the win7 user cant open. There is no
message just nothing happens when clicking to open the .mdb file.
I guess this is some knd of security / locking problem with the .ldb file.
Is it fixed with later updates so should I persist in trying to get Office
updates installed SP1a,2,3 and does anyone know how to do that?
Or there a work around the locking problem.

Gina Whipp

unread,
May 8, 2010, 1:34:14 PM5/8/10
to
Oyster,

Your best bet is to split your application. Having different users with
same operating system trying to open the same database is a recipe for
disaster... so imagine what you are setting yourself for on different
operating systems. Have a look at...


http://www.members.shaw.ca/AlbertKallal/Articles/split/

http://allenbrowne.com/ser-01.html


You may also want to take a look at MVP Tom Wickerath's article...

http://www.accessmvp.com:80/TWickerath/articles/multiuser.htm


To handle the update of multiple front ends see...

http://www.autofeupdater.com/


If each user needs Access you can install the Runtime...

http://www.microsoft.com/downloads/details.aspx?familyid=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"oyster" <u59908@uwe> wrote in message news:a7b3cc9b69c2d@uwe...

oyster

unread,
May 8, 2010, 4:45:36 PM5/8/10
to
Gina - what an incredibly helpful post - thank you so much.
I will definitely split now, and read all the links, and report back
thanks again

Gina Whipp wrote:
>Oyster,
>
>Your best bet is to split your application. Having different users with
>same operating system trying to open the same database is a recipe for
>disaster... so imagine what you are setting yourself for on different
>operating systems. Have a look at...
>
>http://www.members.shaw.ca/AlbertKallal/Articles/split/
>
>http://allenbrowne.com/ser-01.html
>
>You may also want to take a look at MVP Tom Wickerath's article...
>
>http://www.accessmvp.com:80/TWickerath/articles/multiuser.htm
>
>To handle the update of multiple front ends see...
>
>http://www.autofeupdater.com/
>
>If each user needs Access you can install the Runtime...
>
>http://www.microsoft.com/downloads/details.aspx?familyid=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en
>

oyster via AccessMonster.com

unread,
May 9, 2010, 10:55:21 AM5/9/10
to
Split successful and no problems (except needing to load the linked table
manager wizard from CD).
Frontends now in All User folder on XP and Win7 computers and backend remains
in original location on network share on XPpro computer.
BUT the original problem remains. I can only get the Win7 computer to see
the backend data if it is the first to open the .mdb and so create the .ldb.
Otherwise the frontend just hangs with the circular eggtimer. The moment the
last computer closes Access the form immediately opens on the Win7.

This could be a Win7 network security problem but I am not so sure.
I think I have seen it before but I cant remember how I fixed it?

Any ideas please, maybe on how to troubleshoot the .ldb

oyster wrote:
>Gina - what an incredibly helpful post - thank you so much.
>I will definitely split now, and read all the links, and report back
>thanks again
>

>>Oyster,
>>
>[quoted text clipped - 31 lines]


>>updates installed SP1a,2,3 and does anyone know how to do that?
>>Or there a work around the locking problem.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/201005/1

Gina Whipp

unread,
May 9, 2010, 1:36:22 AM5/9/10
to
You're welcome!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"oyster" <u59908@uwe> wrote in message news:a7b699ddaa4ab@uwe...

Gina Whipp

unread,
May 9, 2010, 10:40:36 PM5/9/10
to
Make sure the Windows 7 machine isn't trying to open in *Exclusive Mode*.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"oyster via AccessMonster.com" <u59908@uwe> wrote in message
news:a7c01d7da8329@uwe...

oyster via AccessMonster.com

unread,
May 10, 2010, 10:16:48 AM5/10/10
to
OK finally fixed this problem so reporting back for anyone else what I did,
but cant be sure what the critical step was.
1. Compacted and repair both front end (fe) and back end (be) databases and
redistributed the fe
2. Ensured that all the pcs had the same Workgroup name
3. changed win7 network type to home from work
4. Ensured that no other computer had a connection open to be when running
Linked table manager.
I first got a trouble free connection from an old fe but then when loaded the
new fe the problem came back so I think 4. was the critical step, or having a
slightly different fe on each?

Can close this thread for me now thanks everyone


Gina Whipp wrote:
>Make sure the Windows 7 machine isn't trying to open in *Exclusive Mode*.
>

>Split successful and no problems (except needing to load the linked table
>manager wizard from CD).
>Frontends now in All User folder on XP and Win7 computers and backend
>remains
>in original location on network share on XPpro computer.
>BUT the original problem remains. I can only get the Win7 computer to see
>the backend data if it is the first to open the .mdb and so create the .ldb.
>Otherwise the frontend just hangs with the circular eggtimer. The moment the
>last computer closes Access the form immediately opens on the Win7.
>
>This could be a Win7 network security problem but I am not so sure.
>I think I have seen it before but I cant remember how I fixed it?
>
>Any ideas please, maybe on how to troubleshoot the .ldb
>

>>Gina - what an incredibly helpful post - thank you so much.
>>I will definitely split now, and read all the links, and report back

>[quoted text clipped - 5 lines]


>>>updates installed SP1a,2,3 and does anyone know how to do that?
>>>Or there a work around the locking problem.

--
Message posted via http://www.accessmonster.com

Gina Whipp

unread,
May 10, 2010, 11:41:30 PM5/10/10
to
Well glad you got that figured. And it should be noted... I would not run
the Linked Table Manager while others were using it. But glad you noted
that for others to see.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"oyster via AccessMonster.com" <u59908@uwe> wrote in message

news:a7cc5a329727a@uwe...

0 new messages