Let me know what you find out.


>
>
>Craig,
>
>We can make the TTX file in VFP as you said, but the problem still remains that even if the TTX file is created with DATETIME instead of TIME, crystal still thinks that teh field is TIME when it run using the ADO object
>
>This is the auto generated file
>

>; 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		1
>

>
>We 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		1
>

>
>Making 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.
>
>Thanks anyway for all you ideas Craig, I might have to contact Crystal for an answer on this one.
>
>Chris.