As far as I know, Paradox doesn't automatically recreate secondary index 
or .val files. It has no way of knowing how to recreate them because all 
the information needed is stored in those files. The .db file is just a 
flat file of 64K blocks, containing fields with data in them.

My understanding is that the only way to re-create these files once 
they're gone, is manually or through code.


On 10/12/2019 12:26 am, Kevin Baker wrote:
> Tom,
> 
> So the only way the children files would be recreated is if I initiated 
> it through code?  I ask this because to my knowledge I don't have any 
> code to re-index the table, yet the files were recreated.
> 
> This issue has come about because I was looking at doing incremental 
> backups, but have read this wasn't a good ideal due to the children file 
> issue.  My thought was if I had to do a restore of a db, then I could 
> just delete the children and have paradox recreate them.