Possible bug in Data|Query Designer.
Hi Guys,
Converting a query (Search) from date based to datetime based.
In the Query Designer I have added the field, set the Operator to
'Between' and put in "01/02/2009 00:00:00, 01/08/2009 23:59:59" for
Value. AutoSearch & Mandatory set to Yes.
The SQL shows..
"SELECT INVOICES.INVNUMB, INVOICES.MSN,
INVOICES.MODEL, INVOICES.QTY,
INVOICES.JOB_TYPE, INVOICES.JOB_STATUS,
INVOICES.HOURS, INVOICES.DATE_REP,
INVOICES.DATE_IN
FROM INVOICES INVOICES
WHERE ( INVOICES.JOB_STATUS <> 'CA' )
AND ( INVOICES.DATE_REP BETWEEN '2009-02-01 00:00:00' AND
'2009-08-01 23:59:59' )
ORDER BY INVOICES.JOB_TYPE"
Which is fine.
But when I look at the Search|Value again I only see ""01/02/2009,
01/08/2009 23:59:59"
The query does work correctly.
Is what I am seeing in Value correct?
Regards & TIA,
Ian
Converting a query (Search) from date based to datetime based.
In the Query Designer I have added the field, set the Operator to
'Between' and put in "01/02/2009 00:00:00, 01/08/2009 23:59:59" for
Value. AutoSearch & Mandatory set to Yes.
The SQL shows..
"SELECT INVOICES.INVNUMB, INVOICES.MSN,
INVOICES.MODEL, INVOICES.QTY,
INVOICES.JOB_TYPE, INVOICES.JOB_STATUS,
INVOICES.HOURS, INVOICES.DATE_REP,
INVOICES.DATE_IN
FROM INVOICES INVOICES
WHERE ( INVOICES.JOB_STATUS <> 'CA' )
AND ( INVOICES.DATE_REP BETWEEN '2009-02-01 00:00:00' AND
'2009-08-01 23:59:59' )
ORDER BY INVOICES.JOB_TYPE"
Which is fine.
But when I look at the Search|Value again I only see ""01/02/2009,
01/08/2009 23:59:59"
The query does work correctly.
Is what I am seeing in Value correct?
Regards & TIA,
Ian
This discussion has been closed.
Comments
I believe the time is being cut off because it is set to 0. As a test,
try entering a time different than 0 for your first value and see if
that is saved down properly.
http://www.digital-metaphors.com/rbWiki/DADE/Fundamentals/Date_Formatting
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Hi Nico,
Yep, changing the time from 00:00:00 to 00:00:01 did the trick.
However, 00:00:00 is still a valid time, while not so critical in my
applicatopn, if I was data logging, lots can happen between 00:00:00 &
00:00:01.
Regards,
Ian