Default value doesn't work anymore

[Bennov1979]

[FONT=Verdana, Arial, Helvetica]I have a very strange problem. Suddenly the 'default value' option in SQL server doesn't work properly anymore.
I have two the same databases, one on a SQL 2005 server and one on a SQL 2000 server. In a table I have some fields with default value (0). As far as I know this always worked fine. Now, when I add a record all these fields get TRUE as default value. I added a new field with exactly the same properties in the middle. This one also doesn't work properly. When I move the field to the last position it seems to work fine. But when I add a record through a standard form it goes wrong again.

After trying a lot of thinks I just created a new table with only 2 fields ('Number' (primary key) and 'Ready' (bit, with standard value = (0).
I now add the first record: this works fine, the default value of the field 'Ready' changed automatically to FALSE. I now add the second record: here it goes wrong again! The default value for the field 'Ready' for this record changed to TRUE!!

I use this kind of values for years now and it always worked fine. The strange thing is that it happens to two different SQL servers of two different companies in two different cities.
More strange, maybe, is that, when I add records by the SQL management Studio, it works fine!

Can anyone help?

Thanks in advance![/FONT]

 

[georgedwilkinson]

My first suspicion is the UI with which the data is entered. Especially since it works fine in SQL management studio. The default value is just a default: if the UI supplies its own value (whether you intend it to or not), SQL Server will accept that as the real live honest to goodness value.

 

[Bennov1979]

There is no user interface. I just create an ADP file with the data on the SQL server. Now I open the table (like in SQL management studio) and just navigate to the last record. I keep on adding data and the "default value" field is still going wrong! When I add some records in the studio it gets the correct value: FALSE.

 

[Bennov1979]

Problem solved

Problem happens after install of SP for Office 2003. Microsoft already released a hotfix!