Server 2008 Access
I am in the process of upgrading to a new server - going from Server 2003 to Server 2008. I have set up security permissions and shares on the appropriate files and folders, but I am having some difficulty with "read only" permissions being forced. To further explain, we have a folder that contains about 30 different Access Databases that are used by several people in our company. Users can navigate to the new server file location, but when they attempt to run an Access db, they get the error that the database is running in Read Only mode and needs to be saved to their computer. While this is not such a big deal for the application side of the database (it can be pushed out with a batch file initially and for upgrades), this is clearly not an option for the data side of the db. This message is occuring on both Access backed data and SQL backend data with Access frontend. It may be worth noting that it also happens whether we are running Access 2000 or Access 2007 (the databases were created in 2000). This also happens even when we grant the user (either explicitly or through Domain Users) Full control on the folders and files.
I am fairly new to Server 2008, have I missed something in setting up this new server?
Jody Wood
Answers
- ~sigh~ It was OTK (operator to keyboard) error on my part. I did infact share the folder, I just didn't give that share any permissions, so it assumed "read only" for everyone. Gave the proper users "change" permission and all is sunny in my town. Thanks for your input, and sorry for the bonehead move on my part. :-/
Jody Wood- Marked As Answer byAndrew Mason - MSFTMSFT, OwnerTuesday, October 20, 2009 12:43 AM
All Replies
- Did you try accessing the mdb file in "exclusive mode"?
Regards,
Jai - I had not tried that until you mentioned it, but it didn't work either. I just noticed that I couldn't mstsc to the server anymore either, so maybe that has sometimg to do with it. I can still navigate to the shares on the server, just not RDC. Going to check my settings and do a reboot. Maybe a .dll or something has gotten sideways in all of the work I have been doing to it.
Jody Wood - ~sigh~ It was OTK (operator to keyboard) error on my part. I did infact share the folder, I just didn't give that share any permissions, so it assumed "read only" for everyone. Gave the proper users "change" permission and all is sunny in my town. Thanks for your input, and sorry for the bonehead move on my part. :-/
Jody Wood- Marked As Answer byAndrew Mason - MSFTMSFT, OwnerTuesday, October 20, 2009 12:43 AM


