blackrabbit
IS-IT--Management
We are in the process of moving files on our file server from one share structure to a new more organized structure on the same structure.
In my testing I set up a robocopy job to copy a departments files to the new structure and had them test to make sure permissions were good and that data copied ok. They noticed however that when ever they open thier access databases now they get the following error:
The database 'dbname' is read-only
You won't be able to save changes made to data or object definitions in this database
They did confirm to me that they can infact make changes and that the changes were saved when they exit and reopen the db. I chekced the file properties and nothing is set to read only and all share and ntfs permissions are good.
I've spent a lot of time googling this issue and have rebooted the file server as one blog suggested. They are using Access 2003 and I am using Access 2007. When I open them in 2007 I don't get the error but they keep getting it.
They won't let me proceed with the real copy of data/switch over to new shares until this error goes away. I'm looking for a solution that doesn't require me to create a new db and import the old data or do save-as or things like that since they have hundreds of these databases.
I've run into this before years ago and since I don't use access very often I have no idea what the fix was.
In my testing I set up a robocopy job to copy a departments files to the new structure and had them test to make sure permissions were good and that data copied ok. They noticed however that when ever they open thier access databases now they get the following error:
The database 'dbname' is read-only
You won't be able to save changes made to data or object definitions in this database
They did confirm to me that they can infact make changes and that the changes were saved when they exit and reopen the db. I chekced the file properties and nothing is set to read only and all share and ntfs permissions are good.
I've spent a lot of time googling this issue and have rebooted the file server as one blog suggested. They are using Access 2003 and I am using Access 2007. When I open them in 2007 I don't get the error but they keep getting it.
They won't let me proceed with the real copy of data/switch over to new shares until this error goes away. I'm looking for a solution that doesn't require me to create a new db and import the old data or do save-as or things like that since they have hundreds of these databases.
I've run into this before years ago and since I don't use access very often I have no idea what the fix was.