Hello!

Hello!

I am seeing a really odd problem in BDS2K6.

I have a CDS dataset which has an associated provider.
This dataset has 3 date fields, two of which have been
added recently.

The three date fields are, roughly:
- Estimated (new)
- Actual delivery
- Lost (new)(this basically means that we didn't deliver for some reason)

When new items are added to the order and NO DATE is
touched, all is fine. No errors, no problems, zilch, nada.
If, however, one of the other two dates is modified,
upon save the Actual Delivery date - if null - will give a
"0.0 is not a valid timestamp" validation error.

Googling, it seems that this is due to the RTL being
unable to validate a NULL date.

This is, however, really odd, as we are not seeing
anything like this in our main product lines where
dates are pretty common and there can be a few in a
dataset.

So... what do you think is going on here?
Up until we only had 1 date field ,there were no
problems whatsoever.

Ideas?

A