I can work around this in a number of ways. My purpose in posting is to confirm that this is a Crystal problem (as opposed to a problem with the OLE DB provider).

Here's how to duplicate...

1. Create a free table in VFP, with one field being of date type (I named it invdte).
2. In Crystal Reports 9 (sp2), create a new report, using OLE DB to connect to the table. Select fields to create a basic report. Okay so far.
3. Use the selection expert, choose the date field and change the comparison to "is between" and enter some date values.
4. Click Ok and refresh the data.
5. Observe error -

Failed to open rowset.  
Details: ADO Error Code: 0x0004005
Source: Microsoft OLE DB Provider for VFP
Description: SQL: Column 'DATETIME' is not found.
Native error 806.

Also, when clicking on Show SQL Query from the database menu, this is what the WHERE clause looks like.

WHERE  (`test2`.`invdte`>=CONVERT(DATETIME, '08-01-2003', 110) AND `test2`.`invdte`<=CONVERT(DATETIME, '09-15-2003', 110))

I'm not familiar with a CONVERT() function - is CR thinking this is a valid VFP function? I'm assuming the SQL should be valid fox SQL. Is that true? Can someone confirm this seems to be a Crystal problem?