Is Forms 5.0 reaaly Y2K compliant?

From: Breno de Avellar Gomes <brenogomes_at_ieee.org>
Date: Sun, 25 Jul 1999 22:54:56 +0100
Message-ID: <379B87AF.87EC5171@ieee.org>

First I would like to thank those who sent me suggestions (posting Forms: problem with parameter)

After several attempts I am suspecting of Oracle Forms 5.0 minor Y2K incompatibilities.
I have a block with two date fields, formatted as YYYY-MM-DD. The application is working correctly, except when calling Reports 3.0.

I am passing the following parameter line to Reports:

sql_stat := 'WHERE CALIBRACAO.PROXIMA BETWEEN ''' || :DATE_BLOCK.START_PLAN || ''' AND ''' || :DATE_BLOCK.END_PLAN || ''' ORDER BY CALIBRACAO.PROXIMA';
Works fine until 31-DEC-99. Returns 00 for 2000. (where are the other two digits, even for 1999?)

Trying to convert back and forth
sql_stat := 'WHERE CALIBRACAO.PROXIMA BETWEEN ''' || TO_DATE(TO_CHAR(:DATE_BLOCK.START_PLAN,'YYYY-MM-DD'),'YYYY-MM-DD') || ''' AND ''' ||
TO_DATE(TO_CHAR(:DATE_BLOCK.END_PLAN,'YYYY-MM-DD'),'YYYY-MM-DD') || ''' ORDER BY CALIBRACAO.PROXIMA';
Same result above.

Desperate try 1, knowing it was wrong: direct conversion to char

sql_stat := 'WHERE CALIBRACAO.PROXIMA BETWEEN ''' ||
TO_CHAR(:DATE_BLOCK.START_PLAN,'YYYY-MM-DD') || ''' AND ''' ||
TO_CHAR(:DATE_BLOCK.END_PLAN,'YYYY-MM-DD') || ''' ORDER BY

CALIBRACAO.PROXIMA';
ORA-01861 literal does not match format string Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading white space). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra white space.

Desperate try 2, even worse conversion
sql_stat := 'WHERE CALIBRACAO.PROXIMA BETWEEN ' || TO_CHAR(:DATE_BLOCK.START_PLAN,'YYYY-MM-DD') || ' AND ' || TO_CHAR(:DATE_BLOCK.END_PLAN,'YYYY-MM-DD') || ' ORDER BY CALIBRACAO.PROXIMA';
ORA-00932 inconsistent datatypes
Cause: One of the following:
An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields) or concatenating a character field with a long field.
An attempt was made to perform an operation on a database object (such as a table or view) that is not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object's name.
An attempt was made to use an undocumented view.

Please send me suggestions and comments.

Thanks in advance.

Regards,

Breno

Received on Sun Jul 25 1999 - 16:54:56 CDT