Frank,

I checked the source code again, so I'll have to amend what I said in the
previous post.

It appears the AAMMDDHHMM format is being used.  In Growthpower, when a new
record is put to the SOL-TRANSACTION dataset, a backward chained read is first
done using the sales order line number to find the last record that was entered.
Then it checks the date and time for the new record (in YYMMDDHHMM format)
against the date and time for the last record (in AAMMDDHHMM format) in the
chain.  If the last date and time are >= the new date and time (i.e if
"A001041215" >= "0001051215") the minute part of the new date/time string is
incremented by one until the new record's date and time is greater than the last
record's date and time.  This is done so that two puts in the same minute will
be sorted correctly.  Since the new date and time is in YYMMDDHHMM format, and
the old date and time is in AAMMDDHHMM format, the comparison will always fail
when you enter 2000.

If that loop ever exits (which it won't after 1/1/2000), the new date and time
are converted to an AAMMDDHHMM format, then put to the datebase.  It appears the
problem is the new date and time are not converted to the proper date format
before the backward chained read.  Have you called this in to Pivotpoint?

Bob