Hi,

Here is the code that I execute:

TABLE FILE ACC_PREDICTIONS
PRINT
MIN.BMA_LIBOR
BY WEEKS
WHERE ( UPDATE_TIME EQ '06/01/2005' );
END

and this is the error I get:
(FOC1400) SQLCODE IS -3030 (HEX: FFFFF42A)
: [22005] [Microsoft][ODBC Microsoft Access Driver] Data type mismatch in
: criteria expression.

If I comment out the WHERE line I get data. This is what I have in the master file for the UPDATE_TIME field:

FIELDNAME=UPDATE_TIME, ALIAS=UPDATE_TIME, USAGE=MDYY, ACTUAL=DATE,
MISSING=ON, $

If I just do:

TABLE FILE ACC_PREDICTIONS
PRINT
UPDATE_TIME
END

I get this:

UPDATE_TIME
09/27/2004
09/27/2004
09/27/2004
....

Has anyone seen this before? Any ideas?

This message has been edited. Last edited by: Kerry,

Try taking the quotes and slashes out of your date literal to start. If that doesn't work, talk to someone who is doing straight sql into Access and find out the true date format and use that.

Capture the SQL and see how iWay is presenting the WHERE clause to Access.

Aside from any DATE field issue, PRINT and MIN. don't go together. Try is with SUM.

As Ginny infers in her remarks, there is a difference between what you see when printing a field (as determined by USAGE=) and what you should use in your selection criteria (as determined by ACTUAL=). You need to find out what the real format of the date is (20040927 or 2004-09-27 or 09-27-2004 or one of hundreds of variations) in the database and set the format in your selection criteria to match it.

Hi all,
Thank you for your suggestions, I've tried everything and when I didn't know what else to do I asked some other people in our company for help. They opened a case with IBI and got a solution. The change we had to make was to add a SQL setting code to the edasprof of the sub server (in our case the Wintel reporting server). And now my dates are working fine.

Regards,
Luminita

Can you tell us what the setting was and could you put [SOLVED] in the topic heading?

Thanks.