Read-only problems after split

[cstanley]

Help!

I've split my database and posted the back-end on the network, and rolled out the front-end to other users. It works great on my machine, but other users, when they open the front end, get a message that the database is read-only, and cannot make any alterations to the back-end (even some queries won't run).

I've done the following:

1.) Made sure that the "Read-Only" boxes are unchecked for both the front-end and the back-end.

2.) I'm not using security, but I went in and made sure that the Admins and Users had full permissions, and copied my System.MDW file to the users computers.

What is going on? Does anyone know?

Thanks!

Chris

 

[jeremie_ingram]

Have you check the level of security assigned to the shared drive / folder? In most environments this is inherited, so if the folder has restrictions, they are applied to everything in it.

 

[Steve Kendrot]

Did you fix it?

Chris,

I am having the exact problem you described. I know it was several months ago, but did you fix you problem and if so, how?

Thanks.
Steve Kendrot

 

[cstanley]

Steve,

It was the security of the network folder where the back end was stored - people needed to have read/write access to it. It was a simple fix. Check the "Properties" section for the folder on the person's computer that isn't working to see if they have the correct access. If they don't, get your network admin to grant them the access or move the back end to a more public folder.

Hope this helps!

Chris

 

[Steve Kendrot]

Thanks for your reply Chris. I don't beleive that is my problem. I have already checked the share settings for my BE folder. I think I have screwed up somewhere in my implementation of user level security. Thanks anyways!

Steve

 

[cstanley]

Another option you can try is setting the Access user-level security privleges on the front & back ends to allow everyone Admin level access for the whole dbase. Give it a shot!

Chris