Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Cannot edit this cell". Why?

Status
Not open for further replies.

Jerrycurl

Programmer
Aug 4, 1999
85
US
We just upgraded our SQL 7 server to SQL 2000. When I open a table in enterprise manager, order the rows, and try to edit a field, I get the message "Cannot edit this cell". It doesn't happen for every table, and it only happens if the rows are sorted by certain columns. It's only the column that the rows are sorted by that can't be edited. If I remove the ORDER BY, I can edit with no problems. It goes without saying that this was not a problem before we upgraded. Anyone know what could be causing this? Thanks.
 
I haven't seen that but I have received a 'Firehose mode' dialog when trying to close the results pane in Enterprise Manager. I know you can't edit blobs and I think that you can't edit caculated columns. Is the cell you're trying to edit the pk? JHall
 
I get the message regardless of whether the column is a PK or not. And they're not blobs or anything fancy; just ints and varchars.
 
Could any other entity be locking the records or tables? JHall
 
It can't be a locking issue because it only occurs when I have an ORDER BY in the select statement. If I take out the ORDER BY, it works.
 
That's freaky, I order by and edit in the EM table results pane all the time...
I'll keep my eyes peeled to see if it ever happens to me. JHall
 
I did it all the time, too. It must be some kind of side effect of our upgrade to 2000.
 
If anyone's interested, we've talked to Microsoft about this and they have confirmed that it is a bug. Apparently is was introduced in SP1 because it does not happen in the RTM build. In order to rectify the situation, I set up a test server with the proper collation (Latin1_General_CI_AI), recreated all my objects from scripts, and DTSed the data over. I then reinstalled SQL on our production server with the proper collation and used the Copy Database Wizard to copy everything from test to production.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top