We had a similar situation, and resolved it with a couple of steps. We lowered our history paramater to 365 days, which eliminated surpassing the 99,999 sequence number problem. Each month, the older records are "purged" to the YTH file. Instead of writing this file off to tape (as is suggested), we just leave everything in that file. In the rare occurance we need to pull history that is older than one year (we are a food manufacturer, so it happens!), we use a query tool over the YTH file to access the information. (Overlapping sequence numbers isn't a problem in YTH, as you can sort the records pretty accurately with the date/time fields.) This has also considerably speeded up response time in many applications, as our ITH file is very large. Hope this helps! Lisa Abney Sensient Flavors Indianapolis, IN Syed Arif Inam <arifinam@xxxxxxx To: "SSA's BPCS ERP System" om> <bpcs-l@xxxxxxxxxxxx> Sent by: cc: bpcs-l-bounces@xx Subject: ITH Seq# > 99,999 drange.com 04/16/2003 01:28 PM Please respond to "SSA's BPCS ERP System" Hi, We are facing a problem with ITH Seq# field. Some of high transaction items' ITH seq# value has reached greater than 99,999 and the system is creating transactions with zero seq#. We have to keep 3 years of history and these items have reached the limit in less than 3 years. Has anybody came across this problem? Thanks Ver 4.05CD Syed Arif Inam Dey, L.P. Napa, California __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.