I have a VB 6.0 app running against a SQL Server database.
It has been running fine until recently when something changed and I do not know what caused the change.
When I do an .AddNew to a recordset, it used to set all fields in the recordset to Null. I sometimes used this fact in called subroutines to know that certain initializing work needed to be done.
However, now it sets all fields to an empty string, including dates and numeric values. IsNull is false, Len() returns 0 and the immediate window shows no value for the item.
What could be causing this?
P.S. I have figured out that what I should have done was see if the EditMode property of the recordset was equal to adEditAdd. I have now done this but would still like to know what might have happened. Thanks.
It has been running fine until recently when something changed and I do not know what caused the change.
When I do an .AddNew to a recordset, it used to set all fields in the recordset to Null. I sometimes used this fact in called subroutines to know that certain initializing work needed to be done.
However, now it sets all fields to an empty string, including dates and numeric values. IsNull is false, Len() returns 0 and the immediate window shows no value for the item.
What could be causing this?
P.S. I have figured out that what I should have done was see if the EditMode property of the recordset was equal to adEditAdd. I have now done this but would still like to know what might have happened. Thanks.
