Annoying message

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I still am getting an annoying message on startup of a networked database.
The message is:
"You do not have exclusive access to the database at this time. If you
procedd to make changes you may not be abke to save them at this time."

Please help me please!!

I want ot be rid of this message!!

Cheers,
 
With recent versions of Access (actually since version 2000), you need
exclusive access to a mdb in order to make design changes.

You should split the database. Put the backend on the server, and give each
user a copy of the frontend on their workstation. Then you can make all the
changes you want in your copy of the frontend.

Backend - contains just tables/relationships
Frontend - contains all other objects, and linked tables (linked to the
backend)
 
I recently converted 8 databases to ACCESS 2003 from ACCESS 2000. The new
machine they are running on is using Windows Server 2003. I am also getting
the "annoying" message that IAN mentioned but only on one of the databases.
The first user can open the database (user does not have full control) but
any other user trying to open the database must respond to the message 31
times (exactly - everytime) and then they can open the database and it then
works fine.

The ACCESS 2000 database worked just fine for many years running under
Windows 2000 but not now. With ACCESS 2000, if I as the administrator tried
to modify a table, macro, or form when a user had the database open, ACCESS
would warn me that the change could not be saved. Now it warns me 31 times
when I am just trying to open it.

The solution cannot be to divide the database. In fact since the other seven
are working fine, that solution does not appear to be a solution.

Thank you
RuthAnn Wilson
Mohave Community College, Kingman AZ
 
Do the 31 messages seem to occur when the database is executing VBA
code, as part of its startup? See if you can find that out, & post back
here with the code that is causing it.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
No VBA code. I also noted in several other threads that others were having
the same problem and always 31 messages. One person gave a work around which
does work which is to open Access first and then the database but I really
cannot ask users to do that.

The only difference between this database and the others was that it was
password protected. I actually removed the password and reconverted but that
made no difference still 31 messages.

Thanks
RuthAnn
 
Yes guys,

I get this annoying message exactly 31 times as well!! It only occurs when
a user has the database open and then another user tries to open the same
database. The annoying message does not occur if only one uesr has the
database open..

Anyone know the fix for this problem!!

please advise

cheers
 
How do you tell if the message is an Access error message or an Operating
System Message?
 
I would try to fix this problem with a "divide & conquor" approach.
Successively delete modules, forms, tables, and so on, narrowing down
the possible cause, until you eventually find it.

So, start by taking a copy of the database. (Obviously you do not want
to do this on the real one!) Make sure the problem still occurs in the
copy. Then, delete (from the copy) all of the forms that are not part
of the startup process. See if the problem still occurs.

o If it *does*, then, the problem is probably nothing to do with
those forms. Take a copy of the new version of the database (so you can
go back to this point, if required). Then delete some modules, queries,
tables, or whatever, that also are not part of the startup process.

o If it *doesn't*, then, the problem is something to do with those
forms: start again, this time only deleting half of them, until you
eventually narrow it down to a single form.

Although that proces sounds crude,. it is actually quite effective.

Remember to take a copy of the database after each step. Otherwise, you
can't go back one step to try something else - you have to start the
whole process again!

Post back & tell us what happens.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
The message is an Access message. The exact message is "You do not have
exclusive access to the database at this time. If you proceed to make
changes, you may not be able to save them." There is a box for show help that
goes into more detail and will link me to the Microsoft website for even more
information. You must respond to this message 31 times and then the database
opens and works ok.

Again the message does Not appear if you open Access first and then the
database. Which is not an acceptable solution for my users.

The only difference between this database and the ones that work was it was
original password protected.

RuthAnn
 
I can do as you asked but I do not see the point. The only thing that I have
set to start during startup is the switchboard which I already disabled but
it still happens.

Do other forms or macros just happen because................???? This might
give me a clue where to start since this database has a couple of hundred
forms and macros.

Thanks

RuthAnn
 
RuthAnn,

I have the same exact problem. I tried importing all my objects into a new
database, but still have same issue. I turn off all startup forms, scripts,
etc and still prompts. Other mdbs do not do this and the only thing I can
see is that the one having the problem is about 53 mbytes, others are around
3-5 mbytes. They all have linked tables back to SQLServer. I know this is
getting very frustrating for the users.

What's interesting is that this message only shows up in Access2003. If I
open the database in Access2000, no message is displayed.
 
I have now converted 21 Access databases. I know quite a few but my community
college uses them for everything from managing its Dental Hygiene Clinic, to
its Continuing Education Program, Early Warning System, and Faculty Reviews.
Anyways, now I have two databases with the problem. One is quite large (600
m) and one under 20 m. Neither link to SQL. One which is nearly 300 m is
having no problems.The only thing that makes the two which are receiving the
error similiar is they were both password protected. All 21 link to tables in
other databases and have databases linking to them. Go figure.

I am still hoping that MS has an answer. I would be willing to send them the
database if it would help.

RuthAnn
 
You asked a question and have poo pooed several possible solutions. What's up
with you? Do you want someone to wave a magic wand and your db problem will
be solved?
You should split as Joan first stated. Someone else suggested copying all
the objects into a new database. That should get rid of any password
problems. How many different passwords can (could) be used to open the db?

I have now converted 21 Access databases. I know quite a few but my community
college uses them for everything from managing its Dental Hygiene Clinic, to
its Continuing Education Program, Early Warning System, and Faculty Reviews.
Anyways, now I have two databases with the problem. One is quite large (600
m) and one under 20 m. Neither link to SQL. One which is nearly 300 m is
having no problems.The only thing that makes the two which are receiving the
error similiar is they were both password protected. All 21 link to tables in
other databases and have databases linking to them. Go figure.

I am still hoping that MS has an answer. I would be willing to send them the
database if it would help.

RuthAnn
RuthAnn,
Click to expand...
[quoted text clipped - 28 lines]
Click to expand...
 
I ended up deleting ever maco and ever form which left only tables (I removed
all linked tables) and queries.

I still get the message - 31 times.

Now what?

RuthAnn
 
Personally? I would compact the database & make sure the problem still
occurs; then start deleting all the other objects - as I explained
before. There must surely come a point, where the problem stops
occurring. At that point, you know that the problem is related to
whatever you deleted in the previous step. Or alternatively, if the
problem *doesn't* go away, and it keeps happening even when you have
deleted everything - this is still useful information in terms of
finding where the problem lies.

It's a (possibly frustrating) process of logical elimination of
possible causes.

I assume that you are doing all this on a /copy/ of your database & are
saving a copy of each step.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
Back
Top