T
tbergman
Guest
For new records, a workaround may be to simply not assign the field value at all. I've done this for strings and dates, not sure about integers as I don't think we ever have unknown integer values in my use cases. Another possibility, which I have not tested, is to try using System.Convert
BNull instead of System.DBNull:Value.
Continue reading...

Continue reading...