error msg "Cannot update. Database or object is read only '

Joe8915

Registered User.
Local time
Today, 10:24
Joined
Sep 9, 2002
Messages
820
I now have error message "Cannot update. Database or object is read only ". I know what it means in access but since we migrated to SQL I can't figure this one out. Here is the strange thing, but when I edit the record it updates.

Running MS 2007
 
The message is not referring to the back end, but the Access front end. Is the front end shared?
 
Coach, thanks for the quick response. We are in the testing mode as you can tell. I just confirm that the front end is not shared. I am the only one on the sever.
 
Coach, thanks for the quick response. We are in the testing mode as you can tell. I just confirm that the front end is not shared. I am the only one on the sever.

You posted in the other thread how you found out about needing the PRIMARY key to be set as a primary key. If you did this AFTER the tables were linked, you should delete them from the Access frontend and relink again so that this will come across. It doesn't seem to just propogate through to Access when you make structural changes on the SQL Server to Access. You might not need to delete and relink, but you might use the Linked Table manager to select all of the SQL tables, click the button to have it always ask, and then link to the same ODBC connection again and see what happens.
 
Bob, I tried it and I get the same error. I wish I would have mention this earlier. I can write directly to the table without any problems. But when I have it located on a form that is where error comes into play. Its really a subform on a form, if that makes any difference. I tried directly to write to the subform and got the error. So at least I got it down to the subform.

So here is the bottom line I can write directly to the table and no errors. But going thru a subform I get the error. What I am thinking is do a new form and see what happens. I will keep you updated, like you really wanted to hear that.

O this is so much fun.
 
Bob, I tried it and I get the same error. I wish I would have mention this earlier. I can write directly to the table without any problems. But when I have it located on a form that is where error comes into play. Its really a subform on a form, if that makes any difference. I tried directly to write to the subform and got the error. So at least I got it down to the subform.

So here is the bottom line I can write directly to the table and no errors. But going thru a subform I get the error. What I am thinking is do a new form and see what happens. I will keep you updated, like you really wanted to hear that.

O this is so much fun.
It probably does have to do with either the master/child links you've set if you have the subform's recordsource as the TABLE and there are no other tables linked or anything and you still can't edit. Also, make sure that the main form's Allow Edits is set to YES as well as the subform's.
 
In the Sub form's record source, as you including the primary key field?

AFAIK, with Jet/ACE (access) databases you can get by with leaving this the Auto number primary key. With MS SQL Server, you can't.
 
Ok, guys found my problem, I had some code running in the back ground, that I kinda duh ........ forgot about. I deleted the code and now it work just fine.

Still in testing mode. I have an easy question here. I am trying to see if one of my tables are updating in SQL. Being new with this SQL, I have a table that is called Mod log (two separate words). Running a query to view if the record is being updated, but I can't seem to write the correct query to recognize the table.
So bottom line, how do you write a query in SQL that has a table with split words (Mod log)?
 
I do not use spaces in any object names (except perhaps reports if I want to make a friendly name so I use my list box code to display the names automatically there). Any names with spaces need to be enclosed in square brackets.

So something like:

SELECT LogDate From [Mod log] WHERE [Some Field] = 'Something'
 

Users who are viewing this thread

Back
Top Bottom