Access 2003 database backend has stopped allowing sharing

[JaneE]

I have a database consisting of a backend on the server with front ends on
various workstations. It was written in Access 2000 and converted to 2003 in
January. In March, the server software was upgraded to Server 2003 (which
may have nothing to do with the problem but I mention it for completeness).
The backend has recently stopped allowing sharing. I have reset
permissions, checked that it is still set to open as a shared d/b, set the
folder on the server to Shared but nothing has worked.

I would be most grateful for any suggestions.

 

[Klatuu]

Is the back end an mdb or is it SQL Server?
If it is an mdb, was it also upgraded to 2003 format?
Did you check the sharing and locking options in the back end?
Have you done a compact and repair on the back end recently?
Have you tried relinking to the back end?
Be sure all users have read/write/delete permissions in the folder where the
back end is located.
Do you have SP 3 installed for all users?
Do you have The SP 3 Hotfix installed for all users?
Are all users running full access or on the runtime. SP3 and the Hotfix
don't apply to the runtime.

 

[JaneE]

Thanks for such a quick response.

- Back end is an mdb
- Yes, it was upgraded to 2003 too
- Yes, sharing and locking options checked in the back end
- It was working OK after the last compact & repair that I did, doing this
again has not helped.
- Yes, I've tried relinking
- Yes, SP3 installed on all workstations
- Sp3 Hotfix on at least some workstations but maybe not all (I'd have to
check them)
- All users running full access

Jane

 

[Klatuu]

I did not see an answer to this question:
Be sure all users have read/write/delete permissions in the folder where the
back end is located.
This is important. If a user doesn't have write and delete permissions,
this can happen.
The first user to open the fe will cause the be to open and they have to be
able to create the ldb file. The next user will then create an entry in the
ldb file. If they cannot write to the ldb, they will not be to use the be.
You may need to check with your network people on this.

 

[JaneE]

I am so sorry. I thought I had replied to all questions, but I can see that
I didn't.

I believe that the permissions are correct but I will double-check. I'm in
England so have finished for the day and am replying from home. I will check
in the morning, UK time, and post another reply.

Jane

 

[JaneE]

Hello again.

It was, indeed, a permission problem. There doesn't seem to be a "delete"
option but, by setting users to be able to Modify, the database once again
permits sharing. This may not be ideal, but at least they are working again!

Many thanks for your help. I am extremely grateful.

Jane

 

[Tony Toews [MVP]]

It was, indeed, a permission problem. There doesn't seem to be a "delete"
option but, by setting users to be able to Modify, the database once again
permits sharing. This may not be ideal, but at least they are working again!

I suspect that your IT department set the permissions on the BE MDB.
However when it is compacted a file called db1.mdb is created, the
data copied to it and, if successful, the original BE.MDB is deleted
and db1.mdb renamed to BE.MDB. Thus the permissions the new BE.MDB
file would have are the default permissions for the folder and not
those previously set on the BE.MDB.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[JaneE]

Thank you, this is most enlightening, Tony. It explains a lot. I am very
grateful.

Jane