Hi, Creating a type-19 file (or type-1) has advantages with large records IF you are not doing many reads and writes to the file. If you are updating a type of log record, look into using OPENSEQ, READSEQ, WRITESEQ, instead of READs and WRITEs. With the SEQ functions, you are appending everything at the bottom of the record. Tom RATEX Business Solutions
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Raymond P. de Bourbon Sent: Tuesday, October 20, 2009 11:58 AM To: U2 Users List Subject: Re: [U2] Sequentially Hashed Files Thanks for the response.. Here's my situation: The app is generating records with sequential numeric keys and over time the records are deleted with the file returning to a count of zero.. The record sizes can vary considerably from record to record... Currently we are using dynamic files and are constantly having to resize and generally having to "maintain" the files, and it is becoming quite a headache for us .. Right now, we are just looking for other options and I had seen sequentially hashed files in the manual, and it said that they are bested suited for cases with sequential keys (but says nothing about create not delete etc) - so I thought I would ask... Looks like we may just have to spend time working on some admin scripts to maintain the dynamic files "automatically"... Ray _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
