You do not have exclusive access

[jdurell]

Hello,

I have recently installed Access 2003 on several computers that are
accessing a microsoft access 2000 database. When the DB is opened on a
2003 machine, I am getting that error "You do not have exclusive
access," popping up. This is fine as I did not have exclusive access
but you have to hit enter roughly 20 times before it will let you in,
then everything works perfectly. I would not have any problem if the
error came up once, but as often as it is, can be quite a pain. It may
have something to the startup form but I can't imagine what. It has no
load events.

I appreciate any assistance you can offer.

 

[larrylinsonjr]

MDB is obsolete; don't use it for anything
It cannot be relied upon for a single record nor a single user

-Larry Linson, Jr

 

[BruceM]

I cannot answer your question, but you need to ignore the notorious
troublemaker who signs himself larrylinsonjr. He has an axe to grind, and
is unfamiliar with the capabilities of Access.

 

[BruceM]

I need to add that there is a Larry Linson who is an Access MVP, and who
regularly provides valuable information in this forum. The person who
responded to your post is using a similar name, but is a different person.

 

[Granny Spitz via AccessMonster.com]

I have recently installed Access 2003 on several computers that are
accessing a microsoft access 2000 database. When the DB is opened on a
2003 machine, I am getting that error "You do not have exclusive
access," popping up.

Multiuser databases shouldn't share the same file. You need to split the
database into a front end (forms, reports, queries, etc.) and a back end
(tables and relationships). Place the back end on the server and link to
these tables from the front end, then distribute a copy of the front end to
every user's desktop so each user has their own copy.

This is fine as I did not have exclusive access
but you have to hit enter roughly 20 times before it will let you in,
then everything works perfectly.

If it's 32 times it's the Adobe toolbar for Office causing it. Disable this
toolbar for Access and leave the other Adobe Office toolbars alone.

 

[aaron.kempf]

MDB multi-user database shouldn't share the same BACKEND either

desktop to desktop replication is TOO complex

keep all your data in ONE PLACE; use Access Data Projects
no linking; no frontend/backend.. nothing complex.. just dive in and
go!

and there are REAL ENTERPRISE LEVEL TOOLS for ETL, Development.
Access MDB is a friggin joke kids

-Aaron

 

[jdurell]

Granny Spitz,

Thanks for the help. It was the adobe toolbar (which is never used)
that was causing it. Now I don't look like an ass for having my
company upgrade to 2003.

We were going to split but it makes getting my many updates installed
very time consuming. I think the next move is SQL.

Thanks again,
Jake

 

[Granny Spitz via AccessMonster.com]

It was the adobe toolbar (which is never used)
that was causing it. Now I don't look like an a** for having my
company upgrade to 2003.

We were going to split but it makes getting my many updates installed
very time consuming.

Doesn't have to be: http://www.granite.ab.ca/access/autofe.htm

Thanks again

You're welcome, Jake.

 

[aaron.kempf]

yes.. but then how do you decide which tables go in the frontend and
which in the backend?

ADP is a much much simpler architecture; throw MDB away

-Aaron

 

[Tony Toews]

MDB is obsolete; don't use it for anything
It cannot be relied upon for a single record nor a single user

-Larry Linson, Jr

This is a fraudulent posting not by Larry.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm