>>My findings are that the performance of the WinDev application is at least equal to the VFP version, if not a little faster.
>
>Can you be a bit more specific later on in diffentiating between programming language and data access speeds ?

Sorry Thomas, I am talking about how fast the WinDev application runs - in this case how fast it can extract the zip files, read in the VFP data and write that data into its own HyperFile database. This process, which can involve thousands of update records being written into many files, some of which already contain millions of records, is at least as fast as the VFP equivalent program if not perhaps a little faster.

The IDE is faster to work with simply because it is years ahead of VFP IDE - it is modern, integrated, feature rich, etc.


>>I find that WinDev HyperFile index files are much larger than VFP CDX files. I understand that WinDev builds in a lot or extra space for future record additions so not sure if that is the main cause but they are about 2 or 3 times larger. The database also has various functions you can call / access to calculate statistics, optimize the indexes, etc.
>
>Partly OT: when I know the the read/write ratio is large, I compress the dbf and fpt. In Windev index might be added to such a list...

WinDev handles this for you already. For example,there are several ways to optimize the indexes - you can choose to not let WinDev collect database statistics (used to produce reports on performance of the database for example), you can tell WinDev to optimize the index for reading or optimize for writing, depending on the usage of the database in real-world. WinDev can also handle reindexing the files when it determines that it would be beneficial to do so (optional). When you delete records they are not RECAL'able. But they are automatically re-used by WinDev as needed (so if you want to be able to recall records you need to move them to a backup table for that purpose - a simple 2 or 3 function call to implement). Memo field compression is built in as is memo field optimization.