Solution has been found !
Daylight savings time and different machines set to differnt timezones.
The application is only concerned with dates and does not set time, but
Ingres accounts for it and sets the time back or forward.
so date=date no longer works.
This is because of the 3 eastern states in Australia, only 2 have
daylight savings time, which creates all sorts of problems, this was one
of them.
Oh what fun :) I Hate timestamps, why can't there be a simple date ?
And a time ?
Sean Hennessy
Don't Panic Business Management
Betty & Karl Schendel wrote:
The table I'm concernd with is a tickets file sorted by date. The
dates should be d/m/y
if the date format was reset somehow to m/d/y i'd expect errors, 28th
day.
still, might be something like that. See if you can get ingprenv
and "set" output from the problem machine, and one that works.
Unless a broken copy of the app is on the problem client,
it almost has to be environmental.
Karl
_______________________________________________
Users mailing list
Users@lists.ingres.com
http://lists.ingres.com/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.ingres.com
http://lists.ingres.com/mailman/listinfo/users
