T
tracktraining
yes, the second user gets the error.
--
Learning
--
Learning
Graham Mandeno said:Does it behave symmetrically? That is, if you open the MDB first on
computer A then on Computer B, the user on B gets the error, but if you do
it in the other order then A gets the error?
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
tracktraining said:yes, i got the same problem. =(
--
Learning
Graham Mandeno said:Did you try my other suggestions? (Detect & repair and creating a
shortcut)
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
i am using access 2003. Not sure if it happens with other db cuz this is
the
first db that i have worked on.
--
Learning
:
Sorry - I've never seen it nor heard of it before.
What version of Access are you using?
Does the problem occur with other databases, or just this one?
It sounds like there is a problem with the installation of Access. I
suggest you try doing a "Detect and Repair" (from the Help menu) and
also
try compacting and repairing your database.
Also, try creating a shortcut with the following target line:
<path to MSACCESS.EXE> <path to your database>
For example:
"C:\Program Files\Microsoft Office\Office11\msaccess.exe"
"C:\MyFolder\MyDB.mdb"
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
So you find it weird as well...... do you know if anyone else has
encountered
this same problem?
the Default open mode is set to shared.
--
Learning
:
Are you saying that if you double-click on the MDB file in Windows
Explorer
you do get the message, but if you start Access and say File>Open
then
you
don't get it?
That is REALLY weird!
Can you go to Tools > Options >Advanced and see what the Default
open
mode
is set to (Shared or Exclusive).
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi Graham,
I am sure that I don't have any DoCmd.Save anywhere. In addition,
I
will
be
splitting the db. I don't understand why I am getting this error
mesage.
And
I only get it when I click on the db icon. If both users open the
db
via
ms
access then it works (without error)......... but error happens
when
one
clicks on the icon, then the second person clicks on the icon
later
(which
the first one is still log into the db).
Thanks for all your help so far!
-Tracktraining
--
Learning
:
Well, I'm fairly certain there is nothing in that code that is
causing
the
"exclusive access" message you describe.
Are you sure you do not have a DoCmd.Save anywhere in your code?
Also, in a multi-user environment you really should split your
database
into
a shared backend (tables only) and a frontend (everything else).
You
link
the backend tables to the frontend and give the users individual
copies
of
the frontend on their local hard drives.
This has many advantages, including:
- ease of maintenance
- better performance
- less susceptibility to corruption
For more information, check here:
http://www.granite.ab.ca/access/splitapp/index.htm
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
in
message
the mcrHide:
i followed this: http://www.tek-tips.com/faqs.cfm?fid=2562
--
Learning
:
Hiding a window does not cause design changes to a form, or
any
other
objects. What exactly does mcrHide do? All the steps!
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
"tracktraining" <[email protected]>
wrote
in
message
well... the macro is to minimized (hide) the ms access
application
window.
I
have only seen it done using a macro. Can that be done
without a
macro?
--
Learning
:
On Thu, 13 Nov 2008 08:47:03 -0800, tracktraining
yes, I do have a macros called mcrHide -- to hide the ms
access
window
in the
log in form which is the first form to load (start-up)
when
the
user
click on
the db icon. How can I fix this problem? should I take
out
the
mcrHide
macro?
Thanks,
Tracktraining
Yes. It's changing the properties of a form, it seems.
You can use Tools... Startup to hide the database window;
it's
not
necessary
to use a macro to do so. Just uncheck the "show database
window"
checkbox. You
can make it visible again with F11 if you want to work on
database
design
but
not make it (easily) available to your users.
