Asked By Kevin3NF
24-Jan-08 01:54 PM
let me guess...SQL 2005, pre-Sp2? Known bug fixed in SP2. I *think* it had
to do with databases that were migrated from 2000 or the servers were
upgraded.
Where are you trying to change the value...the GUI or a T-SQL statement?
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.