error 3027 after database repair in Access 2003

[Guest]

After compacting and repairing an Access 2003 database I'm now receiving
"Error: 3027 Cannot update. Database or object is read-only." message. The
database lives on a network and both network privileges and Access 2003
privileges allow for updates. There is a front end db linked to a back end db
and it was the back end I repaired. I also refreshed the links after the
repair. The last repair would have been done March/05. Could a service pack
installation produce this behavior? Or is something else going on?

Thanks

 

[Gary Walter]

After compacting and repairing an Access 2003 database I'm now receiving
"Error: 3027 Cannot update. Database or object is read-only." message. The
database lives on a network and both network privileges and Access 2003
privileges allow for updates. There is a front end db linked to a back end
db
and it was the back end I repaired. I also refreshed the links after the
repair. The last repair would have been done March/05. Could a service
pack
installation produce this behavior? Or is something else going on?

I don't know for sure, but this sounds like

Compacting File Resets NTFS Permissions
http://support.microsoft.com/default.aspx?scid=kb;EN-US;295234

--- quote ------
The compact process always compacts the source Access database file or the
Access project file to a new file. The newly created file inherits NTFS
permissions that are different from the source file.

<snip>

In Access 2002 or in Office Access 2003, the newly created file
automatically inherits the default NTFS permissions of the parent folder of
the Access database file or of the Access project file.

<snip>

Workaround

<snip>

....assign appropriate permissions to the parent folder of the Access
database file or of the Access project file.

--- unquote ---

Is there a chance you had full permission for the *original*
Access file, but "read-only" permission for the folder
it was in?

good luck,

gary

 

[Guest]

No that doesn't seem to be the problem. The folder has "list folder contents"
and the databases (both front and back) have full control. But thanks for
your quick response.

 

[Guest]

After much hunting and pecking, it turns out that the compact and repair
failed. Using a copy made before the repair, I had to manually remove the
offensive data by copying and pasting the good rows into another table,
delete the orginal table and re-work the relationships to the new table. A
bit frustrating. I had tried exporting to Excel, text file, etc, but I kept
getting an "Invalid Argument" error, so went with the manual route. After all
of that I did another compact and repair and everything seems to be just
fine, including all of the NTFS privileges.

Thanks for your help