; Field definition file for table: ADORecordset NINVREF long 1 NMSDSREF long 1 TINVDATE time 1:23:45 PM NTYPE long 1 NQUANTITY long 1 CDETAILS string 75 string sample value CDATABASEID string 10 string sample value NORIGINALID long 1We can edit this to look like this:
; Field definition file for table: ADORecordset NINVREF long 1 NMSDSREF long 1 ; Note this has been adjusted. TINVDATE datetime Jan 5, 1994 1:23:45 PM NTYPE long 1 NQUANTITY long 1 CDETAILS string 75 string sample value CDATABASEID string 10 string sample value NORIGINALID long 1Making this change then allows the user to use this TTX file to create a report using TINVDATE as a DateTime field, however the actual field will still only display as TIME when the ADO recordset has been passed to it, I am beginning to think this reinterpretation of DATETIME into TIME is a bug in the crystal Reporting engine. Because if you interogate the values on the ADOObject before passing it to the report engine the value will be the full DATE and TIME but crystal will only display the time.