>I recently took over a VFP3 application that, over time, had created this huge history file - at the time, it had about 700,000 records and took up about 300 megs on our server. So, using one of the date fields as my guide, I moved about half of the older records in the file to an "archive" file (on someone's hard drive) to free up some space - at least for a while. Now, only four months later, I'm back where I started - almost 900,000 records and 327 megs of disk space. I was recently reminded of the problem when our midnight reindex job failed because of lack of disk space - and we had over 300 megs free.
>
>Anybody out there had to deal with files like this before? Any suggestions on some way to pare it down to a manageable size? And, any ideas about preventing this from happening in four more months? (our company is growing fast, so I suspect I'll run into this again)
>
>Thanks for any help,
>
>JD

An archive file is a good idea. I will probably ZIP to quite a bit smaller than it is when un-compressed.

As far as paring the file down, that is up to you. Do you need all the information that you are keeping? Are you using fields that could be made smaller (eg. N(10) fields where an integer would do)? Do you have large character fields that would work better as memo fields (eg. most of the data in the field is <20 characters, but sometimes it is way bigger, so you made the field a C(100) I would think a memo field there will save disk space)?

What kind of history are youi keeping?

Joe