>Michel, what database- if I recall correctly, date (as opposed to datetime) field in SQL Server is comparatively recent.
>
>Can you tell us why a calculated field won't be the answer?

When there is a need to apply query on a date and a time value, it is wise to put the value in one and only field, such as a DateTime data type. I have used that for years and never encounter such a situation. On the client side, the database is read only for us. So, we cannot alter the database structure or add new fields in it, for such purpose. The query are pretty small however. So, using the CAST() approach would do.