When my end user clicks on the icon for her MS Access database (the
icon is on her Novell NAL menu) she is successful in opening the
database.

However, when another staff member is using the database she receives
the message that someone is using it and she cannot access it at that
time.

Any suggestions as to what I need to do to resolve this? I guess it
would be a fix to allow multiple users simultaneous access to a MS
Access database?

Thanks in advance, Zuf

Per zufie:
Somebody else might have a better idea, but one approach is to
copy the row tb edited to a work table, let the person edit it
there, and then click a "Save" button to copy it back.

To do that, users have to accept that "Last In Wins"... and,
technically, you'd need to have an error trap to deal with the
small chance somebody else hit "Save" at exactly the same time
for a record in the same block - which would count to ten and
then try the save again.

You can add bells an whistles - like keeping a table of who is
editing what and notifying people on the same record
accordingly...
--
PeteCresswell

zufie wrote:

Does the desktop shortcut have anything like
/EXCL
in the command line?

Under Tools/Option/Advanced is the StartUp option set to shared or
exclusive?

On Sep 23, 10:37*am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Nope, no /EXCEL. I ensured the StartUp option was set to shared.

I compared the StartUp option and other options on the Advanced tab to
a second database also on the NAL menu. Both database have the same
options.

Salad--Could/Would a person's profile be a cause for this? That is,
can a profile become corrupted and thefore interfere with a person's
access to a particular file?

Per (PeteCresswell):
Or, of course, just to the text boxes on a screen if it's a
simple enough situation.
--
PeteCresswell

zufie wrote:

In your case I don't see how. UserA can get in if UserB is not in. If
UserB is in UserA is denied. ULS wouldn't have anything to do with that.

If not affected by startup options or command lines I'd then check
folder or file properties.

Hi,

zufie wrote:
What about the users rights on the folder containing the .mbd file ?

The .mdb file should be located in a folder where all users have read,
write, create, and delete privileges.
So maybe a ldb file could not be created. You can read more about it here:

http://support.microsoft.com/kb/208778

Regards
Jens

"Jens Schilling" <JensSchillingBitteLoeschen (AT) fissership (DOT) de> wrote in
news:i7g1mt$d4f$00$1 (AT) news (DOT) t-online.com:

DELETE is not absolutely required.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Sep 23, 11:10*am, "Jens Schilling"
<JensSchillingBitteLoesc... (AT) fissership (DOT) de> wrote:
it may not be folder permission, it could be windows user groups
I've seen it where userA is a power-user or administrator, and userB
is a regular user
if userB opens the mdb first, userA can also open it
but not vice versa

Hi, David

David W. Fenton wrote:
Maybe you are right - but it is documented in the same wording in the
knowledge base article that I have mentioned.

Regards
Jens