If I, for example, change the column width for a view in an Access Data Project in Access 2003 SP 2 I get this error message:
"Object is invalid. Extended properties are not permitted on 'dbo.view1', or the object does not exist."
To get it:
- SA creates a new database in SQL Server 2000 SE SP4 running on Win 2000 Server Standard SP4,
- SA creates a new view VIEW1 with one field, for example name from syscolumns,
- SA gives login TEST database role db_owner but no server role to the new database,
- I create a new Access Data Project in Access 2003 SP 2, open VIEW1, change a column width, choose Save and get the error. I open VIEW1 again and the width is not changed (but once in a hundred it was).
If login TEST gets server role System Administrators it functions.
Why are extended properties not permitted without being SA At another company with very similiar setup it works perfect, why not here
The solution
barbarian
I'm not sure, but could you verify what is the default database for the TEST login
Is it possible to add "USE" to the view and does it change the behavior
Dan Ward
Sorry Anton but the default database for the TEST login was already the new database.
The solution was to make TEST instead of sa the owner of the database with EXEC sp_changedbowner 'TEST'.