Well - I've noticed the same issue. The problem isn't really with VFP - it's with the ODBC driver (which hasn't been updated in a looong time).
In my case I just continued to use the datetime fields as I did in SQL 2005 for projects I'd already written. I suppose if I come across a NEW sql 2008 table that someone else has made and it has that new Date type field in it then I will deal with that as it comes up.

It would be nice if Micro$oft would update the ODBC driver or some enterprising person wrote a new / better one.

>I've been asking this question for awhile now and have yet to receive any good answers.
>
>So, now I've finally installed SQL2008 on my machine and I built a table and used the new DATE datatype.
>
>In VFP I ODBC'd the table down and GUESS WHAT?
>
>Right! Exactly!
>
>The DATE datatype gets brought down to VFP as, wait for drum roll... A FREAKING VARCHAR.
>
>A VARCHAR!
>
>It's a GD VARCHAR.
>
>Boyz, we are screwed now. I'm running VFP 9 SP2, so there's nowhere to go to get this one fixed.