Fw: removing mass records

[Nancy Palmquist]

David,

Variation on second option:

1) copy key to keyshrink (or some other qualifier)  No deletion is done, 
you just copy what you want to keep.  So all data is maintained.
2) Reset key to zero records and remove indexes
3) copy good records back to key - you still have the old and new in the 
keyshrink so if anything happens nothing is lost.

System maintained fields are a problem in this setup.

Working with the files instead like they are non-filepro files and 
keeping the 20 byte overhead in the first field, will allow you to keep 
all the data stored in the system fields.

This is a trickier setup, since you need to make two non-filepro files 
exactly like the real file except you insert 1 20 byte field at the 
beginning of the file.  This will not work with files split into 
key/data segments.

But you would have one empty and one file would copy all the data to the 
empty file.

Then move the file back to the key position in a real filepro file and 
index.  It should be functional.  I prefer to keep important system 
field data in real fields to avoid worrying about moving the records 
around for archives.

Many archives II use are date related and would hold all records for a 
certain year or month.  Makes it easy to trim your files if you want to 
drop the oldest qualifier.  But since I would lose the @fields when I 
move the records to these qualifiers I keep creation date and created by 
data in the record - as well as other fields if it seems relevant to know.

Nancy

Nancy
On 9/2/2014 3:56 PM, davidrottkamp at echoes.net wrote:
>
>
> Hi
>
>    I wanted to ask what is the best way to remove mass records from a database
>    in older version filepro, index would break down and process would hang.
>
>    I want to make a routine that would delete records based on age, without having to
>    1) remove indexes
>    2) select records (which than takes forever)
>    3) remove records
>    4) copy back indexes and rebuild them
>
>    as this leaves blanks in the file
>    I have also in past used to
>
>    1) copy good records to qualified key
>    2) copy qualified key over key
>    3) rebuild indexes
>
>    problem is if this breaks in the middle I could have a corrupt key file with very few records
>
>    does any one have a better way of deleting mass records and not leaving blanks in the file
>
>
>    Thanks,
>
>    Dave Rottkamp
>    Cell 570-620-8027
>
>    www.poconolakeproperties.com
>
>
>
>
> --------------------------------------------------------------------------------
>          This email is free from viruses and malware because avast! Antivirus protection is active.
>       
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20140902/a0a9463a/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>

-- 
Nancy Palmquist
Owner
Virtual Software Systems - www.vss3.com
(412) 835-9417