The size of the REV files in the application have incereased enormously in a day or so.

The number of records has not changed much but the size of the files has increased from approx 10Mb to 500Mb.

Any suggestions???

You don't say what platform, version or Network product you are using.

Without any of this informationm, I would suggest that you have some sort of corruption of the directory entries.

Is it just one file that has grown, or all files.

[email protected]

My first guess is the same as Tim's, that you have a corrupt file. Another possibility is that the files sizelock is set to 1. This would let your file grow but not shrink. To get a jump in file size that you are talking about would require a very large amount of acctivity with that file.

Michael Slack

Dump the file and look at the header. The size of the LK file should be equal to the modulo times the framesize. Primary % is adjusted automatically to match Threshold % if your sizelock is set to 0 by changing the modulo and redistributing some of the records. If it is set to 1, the file will grow but not shrink. If it is set to a number higher than 1, it will not be resized at all. By default, Threshold % is 80. If this got corrupted, it could be a source of your problem. Unless you have a good reason not to, you should set the threshold to 80 (press F1 in DUMP for instructions on adjusting the various items).

Next, look at the rowcount. Does it seem reasonable? If not, do a COUNT filename (COUNTROWS tablename) to reset the value. If this value was corrupted and is too high, the file will grow to accommodate the high number.

OK. That takes care of the LK file. Now we will consider to OV file. What is your average record size. The size of your OV file in relation to the size of the LK file will be a function of your average record size primarily, as well as the frame size. If your records are small, then the OV file will be smaller than the LK file. If, on the other hand, as with the LISTS file, your records are large, the OV file will be larger. In general, if your records are significantly smaller than your frame size, you should have a smaller OV file than LK file.

However, if you do a lot of purging of records, it may still be normal to have an excessively large OV file. This is because as you delete records, you are creating holes in the OV file. If you think this applies, then you can resolve this problem by compressing the file (again, press F1 in dump for instructions).

if this is a ceridian file take caution. Do not mess with the percentages in the DUMP. MAKETABLE a new file copy all your good records into it, CLEARFILE the original and copy back.

Verify the OV/LK size relationship.

Very simple approach, but it works.

call if you have questions 330-945-5725

www.i3consulting.com

Rich said, "if this is a ceridian file take caution. Do not mess with the percentages in the DUMP. "

Care to explain?

View this thread on the forum...