The only way that I know that this can happen within the UniData engine is by using CONFIGURE.FILE to set MINIMUM.MODULO lower than the modulo they dynamic file was originally created with - and for the file to merge as records are deleted.
This is fixed at 7.2.5 by a change to CONFIGURE.FILE to not allow this setting to occur. So: either upgrade to 7.2.5 or don't use CONFIGURE.FILE to change MINIMUM.MODULO setting to a number smaller than the original modulo - on a file that has the potential for merging. Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 ..Denver, CO 80237 ..USA Tel: +1.720.475.8055 Email: [email protected] Web: www.rocketsoftware.com/u2 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Address Sent: Thursday, May 06, 2010 8:08 AM To: [email protected] Subject: [U2] ERROR IS NOT A UNIDATA DATA FILE How can this happen ? ³ Review Client Billing Registers ³ ³ Client-Based SUTA Tax Registers > ³ ³ Employer 941 Register for Client ³ ³ Find Client from Invoice Number ³ ³ Company Group Benefits ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ >LIST INVOICES File size(204800) is < minimum hash file size, blocksize(2048) * (modulo(101) + 1). D:\ACCOUNTS\DATA\INVOICES\dat001 is not a UniData data file Open file error. We had a similar error earlier this week with another file. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
