Larry,

13Gb is fine. FoxPro's file size limitation, however, is 2Gb, so
a properly thought out archiving strategy is still needed.

Michel.

============================ Original message follows =====================

>>John,
>>
>>The key and only issue here is whether that archive file is CRUCIAL to your
>>business. If it is then you will have to dedicate time to properly
>>program an archiving system. As simple as that.
>>
>>Brad has given you a few ideas, and a proof that large files are
>>handled by FoxPro without problems, etc... At the end of the day,
>>however, if that file is NEEDED by your business, you will have to
>>sit down and think up a proper automated and seamless archiving system.
>>
>>Michel.
>>
>>================== Original message follows =======================
>>
>>>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
>IMHO,
>With the price of a 13 Gig HD at around $300 bucks, the cost effective solution would be to replace the HD. Also it looks like you need to seriously consider moving to a client server system...and soon!
>//:^)