How to avoid error -1210?
Roland Edulsch got error -1210 in an INFORMIX-SQL 6.00.UE2 report on UNIX_SV when entering dates after 28 August 2000. Art Kagel noted ISQL 6.00 is not Y2K compliant and asked about two-digit year format strings. Roland said all dates and formats used four-digit years, unloaded data was correct and a database check found nothing. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello, I recently encountered a problem with a report - maybe someone could help me. I prompt the user for input of a variable of type DATE and use this variable in a subsequent query (something like "...where date <= $input"). This works fine for all dates less or equal the 28th August 2000 (using '28/08/2000' in the input with DB_DATE set to 'DMY4'). Any higher date causes an error '-1210' saying the date could not be converted to an integer because it is out of range. What could be the reason for this behaviour? Did I miss something (maybe a conversion ist needed in my query) ? TIA -- Ronny (mailto:NOSPAM.riscos@gmx.net) (Remove 'NOSPAM.' in e-mail answers)
Version and platform? Tool (D4GL, C4GL, R4GL, PERFORM)? Art S. Kagel Roland Edulsch wrote: > > Hello, > > I recently encountered a problem with a report - maybe someone could > help me. > > I prompt the user for input of a variable of type DATE and use this > variable in a subsequent query (something like "...where date <= > $input"). This works fine for all dates less or equal the 28th August > 2000 (using '28/08/2000' in the input with DB_DATE set to 'DMY4'). Any > higher date causes an error '-1210' saying the date could not be > converted to an integer because it is out of range. > > What could be the reason for this behaviour? Did I miss something (maybe > a conversion ist needed in my query) ? > > TIA > > -- > Ronny (mailto:NOSPAM.riscos@gmx.net) > (Remove 'NOSPAM.' in e-mail answers)
"Art S. Kagel" <kagel@bloomberg.net> schrieb im Newsbeitrag news:39AAB7CD.42F23609@bloomberg.net... > Version and platform? Tool (D4GL, C4GL, R4GL, PERFORM)? > Sorry, missed that... INFORMIX-SQL Version 6.00.UE2 on UNIX_SV 4.0 3.0, trying to run a report with SACEGO. -- Ronny (mailto:NOSPAM.riscos@gmx.net) (For replies via e-mail remove 'NOSPAM.')
ISQL 6.00 is NOT Y2K compliant. Is it possible that the report contains a date with an explicit format string that includes only a 2 digit year? Art S. Kagel Roland Edulsch wrote: > > "Art S. Kagel" <kagel@bloomberg.net> schrieb im Newsbeitrag news:39AAB7CD.42F23609@bloomberg.net... > > > Version and platform? Tool (D4GL, C4GL, R4GL, PERFORM)? > > > > Sorry, missed that... > > INFORMIX-SQL Version 6.00.UE2 on UNIX_SV 4.0 3.0, trying to run a report with SACEGO. > > -- > Ronny (mailto:NOSPAM.riscos@gmx.net) > (For replies via e-mail remove 'NOSPAM.')
"Art S. Kagel" <kagel@bloomberg.net> schrieb im Newsbeitrag news:39ABDDF1.C9AABB0C@bloomberg.net... > ISQL 6.00 is NOT Y2K compliant. Is it possible that the report contains a > date with an explicit format string that includes only a 2 digit year? > No. Alle dates are of the form 'dd/mm/yyyy'. I did an unload of the data which is affected by the selection (without filtering the date fields) to check for possible faulty values in it. All records are absolutely correct and had no unset or illegal date values. The date format in the variable used for comparison is also set correctly. Format strings in the output part of the report do also use the above mentioned mask. This error is very strange, since the report uses a quiet simple SELECT part (only one table and only 4 or 5 WHERE conditions, very straightforward). BTW:Checking the database for possible inconsitencies did not help :-( -- Ronny (mailto:NOSPAM.riscos@gmx.net) (For replies via e-mail remove 'NOSPAM.')