Runtime Error 3436 - Can't use anything in DB

I have a database split with FE on each users hard drive and the BE on a
server. I (the creator of the DB) have no problem using everything in the
DB, however, the other user can't open anything or use any buttons in the DB.
Does anybody know what I did wrong or how I can fix this issue?
--
Thanks.

The error number indicates Access is having a problem creating a file. This
would seem to be a Windows permissions issue.

You say the BE is on a server. When users log in to share the file, Access
needs to create a little LDB file to manage the locking. If they don't have
permission to create this file, you will get this kind of error.

They also need permission to delete the LDB when everyone logs out later.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Melissa" wrote in message
...
I have a database split with FE on each users hard drive and the BE on a
server. I (the creator of the DB) have no problem using everything in the
DB, however, the other user can't open anything or use any buttons in the
DB.
Does anybody know what I did wrong or how I can fix this issue?
--
Thanks.

The user should have permissions where the BE is. I just recently split the
DB. Prior to that, the DB was saved on the server, where the BE is now
saved) and nobody had problems getting into it (as long as I wasn't in it).
Now it appears that nobody can get into it. I'm perplexed. I'm fairly
certain permissions haven't changed on the server so I can't figure out what
could be the problem. --
Thanks.


"Allen Browne" wrote:

The error number indicates Access is having a problem creating a file. This
would seem to be a Windows permissions issue.

You say the BE is on a server. When users log in to share the file, Access
needs to create a little LDB file to manage the locking. If they don't have
permission to create this file, you will get this kind of error.

They also need permission to delete the LDB when everyone logs out later.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Melissa" wrote in message
...
I have a database split with FE on each users hard drive and the BE on a
server. I (the creator of the DB) have no problem using everything in the
DB, however, the other user can't open anything or use any buttons in the
DB.
Does anybody know what I did wrong or how I can fix this issue?
--
Thanks.

Try creating and deleting a file in exactly the path used for your linked
tables. Use Notepad or Word.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Melissa" wrote in message
...
The user should have permissions where the BE is. I just recently split
the
DB. Prior to that, the DB was saved on the server, where the BE is now
saved) and nobody had problems getting into it (as long as I wasn't in
it).
Now it appears that nobody can get into it. I'm perplexed. I'm fairly
certain permissions haven't changed on the server so I can't figure out
what
could be the problem. --
Thanks.


"Allen Browne" wrote:

The error number indicates Access is having a problem creating a file.
This
would seem to be a Windows permissions issue.

You say the BE is on a server. When users log in to share the file,
Access
needs to create a little LDB file to manage the locking. If they don't
have
permission to create this file, you will get this kind of error.

They also need permission to delete the LDB when everyone logs out later.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Melissa" wrote in message
...
I have a database split with FE on each users hard drive and the BE on
a
server. I (the creator of the DB) have no problem using everything in
the
DB, however, the other user can't open anything or use any buttons in
the
DB.
Does anybody know what I did wrong or how I can fix this issue?
--
Thanks.

Check the links to the back-end tables. If you used a shortcut, or a path
from your subdirectory that the other users don't have, then that can cause
this problem. Re-link the tables, navigating from the server connection that
is common to all users.
--
Daryl S


"Melissa" wrote:

I have a database split with FE on each users hard drive and the BE on a
server. I (the creator of the DB) have no problem using everything in the
DB, however, the other user can't open anything or use any buttons in the DB.
Does anybody know what I did wrong or how I can fix this issue?
--
Thanks.

"Allen Browne" wrote in
:

They also need permission to delete the LDB when everyone logs out
later.

No, they don't need delete permission. It may or may not be
convenient to give them that permission, but removing it does not in
any way prevent use of the database. If you want to protect the
folder from a user accidentally deleting the main data file,
removing DELETE permission on the folder is the easiest way to do
it.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"Allen Browne" wrote in
:

Try creating and deleting a file in exactly the path used for your
linked tables. Use Notepad or Word.

The easiest way to test this is to right click the folder and choose
NEW - Text File. If it can be created, *you* have the correct
permissions. But you have to check that someone logged on as a user
has permissions to do that.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"David W. Fenton" wrote in message
36.81...
"Allen Browne" wrote in
:

Try creating and deleting a file in exactly the path used for your
linked tables. Use Notepad or Word.

The easiest way to test this is to right click the folder and choose
NEW - Text File. If it can be created, *you* have the correct
permissions. But you have to check that someone logged on as a user
has permissions to do that.

I've heard of situations where users could not update files created by other
users, so it's useful to ensure that the user not only can create a text
file as indicated, but can make changes to and save a text file created by
someone else.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

"Douglas J. Steele" wrote in
:

"David W. Fenton" wrote in message
36.81...
"Allen Browne" wrote in
:

Try creating and deleting a file in exactly the path used for
your linked tables. Use Notepad or Word.

The easiest way to test this is to right click the folder and
choose NEW - Text File. If it can be created, *you* have the
correct permissions. But you have to check that someone logged on
as a user has permissions to do that.

I've heard of situations where users could not update files
created by other users, so it's useful to ensure that the user not
only can create a text file as indicated, but can make changes to
and save a text file created by someone else.

Good point. Not sure how you'd test that, though.

I would also like to hear what the exact permissions are on the
folder that lead to such a problem. I've never encountered it,
whether on folders for which I'm the sysadmin or for ones where I'm
not. I tend not to use the EVERYONE group, so I'd think I'd be more
likely to encounter problems than others (I use AUTHENTICATED USERS
instead), but I haven't.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"David W. Fenton" wrote in message
36.90...
"Douglas J. Steele" wrote in
:

"David W. Fenton" wrote in message
36.81...
"Allen Browne" wrote in
:

Try creating and deleting a file in exactly the path used for
your linked tables. Use Notepad or Word.

The easiest way to test this is to right click the folder and
choose NEW - Text File. If it can be created, *you* have the
correct permissions. But you have to check that someone logged on
as a user has permissions to do that.

I've heard of situations where users could not update files
created by other users, so it's useful to ensure that the user not
only can create a text file as indicated, but can make changes to
and save a text file created by someone else.

Good point. Not sure how you'd test that, though.

I would also like to hear what the exact permissions are on the
folder that lead to such a problem. I've never encountered it,
whether on folders for which I'm the sysadmin or for ones where I'm
not. I tend not to use the EVERYONE group, so I'd think I'd be more
likely to encounter problems than others (I use AUTHENTICATED USERS
instead), but I haven't.

To be honest, I've never encountered it myself either, and the people who've
posted that that was an issue did not provide sufficient details to know how
it got that way (other than in one case where I believe they were using a
Linux server)

To test it, though, you'd have one user create the text file, and then see
whether other users can make changes to that file and save it.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)