>>'guy across the hall here uses FilePRO and has been for some time (couple of
>>years). he sez that the only time it happened to him the problem was caused
>>by a logic error in his own code.
>Ah...well, I called FilePRO and after checking several things, he
>suggested I just rebuild the indexes. That worked fine. No more
>Also figured out why you have like 5 records, but only one
>there...when you delete records, it just blanks out the data, and then
>reuses them next time you add. *shrug* works for me, i guess.
if you search by index or other way you will not be shown the data.
FilePro keeps pointed information in a linked list. When you delete a
record that record is marked as free to use and will not be displayed
when using any method other than a search by record number.
The records will be reused in the order in which they are removed,
similar in effect to the the way Unix manages it's free list.
By reusing the record the file size never grows to more than the
maximum number of records used. And by re-using, you don't have the
problems that used to plague dBase programmers of having to pack the
database to get rid of empty records. (I haven't been near dBase for
about 8-10 years - so if it's changed don't flame me.).
This method seems to perplex some people - and I wish at times there
was an option to keep the record number from being displayed at the
bottom of the screen. In the lib directory under fp directory you can
run freechain <filename> and it will set the pointer to use the
freed records in ascending order, much like the -s option to fsck.