November 26, 2011 at 9:01 am
We were running SQL 2000 for years and all was well. We upgraded to SQL 2008 Standard Edition.
All Existing Tables are totally accessible and we can add records just fine.
But, All NEW Tables we create are Read Only from VB6.
Yes, I Know... Dump VB6. It's a 10,000 line program. We Can't Do it.
We've checked every permission option we can find.
When we do an AddNew, we get the error 3027 Cannot update. Database or object is read-only.
However, when we log into Management Studio with the exact same user, we can add rows Just Fine!
Help Please
Thanks in Advance. This is driving us nuts... More than we already are 😉
November 26, 2011 at 9:45 am
Here is an article that might explain what you are seeing: http://msdn.microsoft.com/en-us/library/aa337286.aspx
It could simply be the fact that the login through your application does not have VIEW DEFINITION on the objects and therefore it is read only.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 26, 2011 at 9:48 am
Also, verify whether or not there are primary keys defined on the tables. That could also be causing the tables to be read only from ODBC.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 28, 2011 at 2:12 pm
God Bless You. When I added an Index with a Unique Key, IT WORKS! :)))))))))))))))
THANK YOU!
November 28, 2011 at 4:12 pm
Glad to have helped.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply