mdb strange problem

[Kopas]

I have a database (mdb - access version 2003) on a shared folder.
It turns out that users access using version 2003 does not record any problem, however who have the 2010 version suffer from a extreme slowness (opening/closing forms/reports etc..)
This slowness disappears only if (using access 2010):
There are no users using the database, or
The user’s with the 2010 open te database twice (the second opened shows no slowness), or
Accessing the shared database by a front end db (in a not shared folder) with linked tables;

Any advice? Thanks

 

[bob fitz]

Has the db been split.

 

[Kopas]

Hi,

No has been not

 

[The_Doc_Man]

Doing a front-end/back-end split might help.

Keep the back-end as 2003 format. Give everyone private copies of the front-end. You would see improvement.

You would see more improvement if you could ALSO upgrade everyone to Ac2010 and then upgrade the back-end to 2010. However, as long as you have some folks still on 2003, the back-end has to be on 2003.

 

[Kopas]

Doing a front-end/back-end split might help.

Keep the back-end as 2003 format. Give everyone private copies of the front-end. You would see improvement.

Thanks

It is a possible solution, however for some reasons would not like to apply.

Can someone explain why If a user with the 2010 opens the database twice the second one shows no slowness

 

[bob fitz]

A multi-user db should always be split. It is simple to do, Access even has a wizard to do it for you. IMHO you will get no where until it is at least set up properly for multi-users. Not Not splitting it may cause your data to become corrupted at any time, even if has been used for a long time as a single db.

 

[The_Doc_Man]

Can someone explain why If a user with the 2010 opens the database twice the second one shows no slowness

Possibly the presence or absence of the .LDB file, which must be created by the first user to enter the database and which must be deleted by the last user to leave the database.

The second user doesn't have to create the .LDB file but the first user does. If you have a centrally located shared monolithic .MDB file, you have to create the .LDB file in that same shared folder.

 

[Kopas]

The point is that the same user has to keep open the same DB twice, to not suffer from slowness on one (the last opened).

I emphasize that the LDB file is already created by other users that opened the base.

If there is no LDB file (so no users with the DB open) when opening the DB does not show this problem.

It is possible to get around this problem?

Thanks