unable to modify field in SQL Server 2005

15 pts.
Tags:
SQL Server 2000
SQL Server 2005
SQL Server errors
SQL Server migration
I have a database that was working perfectly on SQL 2000. We moved the data to SQL 2005. Now when our program accessing the SQL 2005 Server we get "Field 'optional' cannot modify." The Field optional is a bit field. The program is able to modify other tables in the database. It just won't modify the 1 table. I have checked to make sure that the default value was set in properties for the field. We have changed the security to allow the user ownership on the database, and we still continue to get the error. Any Help will be Greatly Appreciated. RB
ASKED: March 26, 2008  7:43 AM
UPDATED: April 2, 2008  1:31 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

What is the front end program that you are using?

Unless you have removed the users right to modify the column the column should be update-able. There is no way to set a column to be read only.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • only1rb
    We are using a custom application that has been running for the last couple of years. The program was written in Borland Builder 6 C++. The program works perfectly in SQL 2000 but when we switched to SQL 2005 we get the error. Crazy thing is I can write a small app to access the same table and it works fine. I can update, insert, delete, etc..
    15 pointsBadges:
    report
  • Jonsjava
    Out of curiosity, what is upgrading to 2005 buying you? If the application is running perfectly with 2000, and you don't need any of the features of 2005, why upgrade? I'm not questioning your judgment, merely pointing out something that can at times be easily overlooked -- always look at risk/reward when an upgrade could potentially cause issues, while staying where you are will not.
    225 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following