Hi Martin,

Thanks for the explanation.

So when creating embedded SQL you should look at the SQL type of the column (SQL_NATIVE_TYPE) to determine the dummy zero date value.

Our challenge here is really an admin one. We have getting on for 200 clients, some new but many longstanding who will have migrated to SQL using ck 3.x. If we're writing standard reports or standard logic that work in all cases we need to be confident that whatever dummy date value is used is consistent across the board and won't be different from client to client (or even from table to table withing the same database)

I do, of course, appreciate that when connecting to new SQL databases, or when creating new databases it's great to be up to date and use whatever the database will allow. But when working with existing clients, consistency is important too. As long as a value is valid, my preference would be to be able to define a dummy date value and stick to it, so that analysis continues to just work and new clients will see the same values as older ones when migrating to sql, regardless of the ck version.