i don't know why that would be happening, but try turning off the default setting.
Duncan Cumming IT Manager http://www.alienationdesign.co.uk mailto:[EMAIL PROTECTED] Tel: 0141 575 9700 Fax: 0141 575 9600 Creative solutions in a technical world ---------------------------------------------------------------------- Get your domain names online from: http://www.alienationdomains.co.uk Reseller options available! ---------------------------------------------------------------------- ---------------------------------------------------------------------- "Russ 'Snake' Michaels" To: <[EMAIL PROTECTED]> <snake@snakep cc: it.net> Subject: RE: [ cf-dev ] update query 08/09/02 03:02 PM Please respond to dev Amazing, i deleted the column, added a new one with a new name, and this also gets set to zero with every update as well. -----Original Message----- From: Justin MacCarthy [mailto:[EMAIL PROTECTED]] Sent: 09 August 2002 14:58 To: [EMAIL PROTECTED] Subject: RE: [ cf-dev ] update query Sounds like a "Friday" bug, the solution; 2 days drinking, eating and having fun.. Justin > -----Original Message----- > From: Russ 'Snake' Michaels [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 09, 2002 2:49 PM > To: [EMAIL PROTECTED] > Subject: RE: [ cf-dev ] update query > > > sql server 2000 > it's actually called AdminAdded, and does not show as reserved > > > > > -----Original Message----- > > > From: Russ 'Snake' Michaels [mailto:[EMAIL PROTECTED]] > > > Sent: 09 August 2002 15:09 > > > To: [EMAIL PROTECTED] > > > Subject: [ cf-dev ] update query > > > > > > > > > ok check this out. > > > > > > I have a field in the table > > > > > > Admin bit default(0) > > > > > > The value of this field is currently set to 1 > > > I have just changed it to a NOT NULL value with a default, > > > previous is a NULL, still did the same thing. > > > > > > I run an update query, this query DOES NOT update this > > > column. There are no other update queries. Nothing touches > > > this column at all. Yet every time I run an update query, > > > this field gets set to 0 all by itself. there are no triggers > > > or anything of this sort to cause it, it is just a plain old table. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
