"1/1/1900" *is* NULL for a datetime in MSSQL.
I've never heard of that. Are you sure?
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).
If the field is set to 1/1/1900 I can't do commands like "is null" in my SQL statements. Thus I don't believe an actual date value of 1/1/1900 is the same as a null value.
I'm not claiming to be an expert of null values in MSSQL, thus perhaps I just don't understand it enough. But are you sure?
-Jeff
--- 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/
