> I've never heard of that.  Are you sure?

Yes, if you don't explicitly insert "NULL" and the default value of the
datetime column is not set to "NULL" then SQL Server will insert
"1/1/1900" by default.

> If I output the field, it returns 1/1/1900 (not null).  Hoever I can
> actually set the value to null either by using a SQL update statement
> with "update tblName set fieldname = null" or by going into MS SQL
> Enterprise Manager, clicking on the field, and pressing "ctrl+0".
(Thus
> setting it to null, not an actual date field like 1/1/1900).


Yes, it depends entirely on how the tbl is setup and how the data is
inserted. How are ou doing the insert. Are you using the setData method
of you custom type? It's worth noting that Fourq will not insert "NULL"
for date fields. Instead it inserts an empty date (which is *not* null)

~tom

---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to