Rebuild Key File (RKF) Options for BF Files (not Legacy)
Attached is a graphic that visually explains the options. In short to do a proper Rebuild, you have to uncheck both Integrity Check and Optimize File.
If you check either or both boxes then that's all it will do (but not Rebuild).
If you check neither to do a Rebuild, then it will NOT do an Integrity Scan or Optimize.
If you want to combine the options, you have to run RKF separate times.
Should you combine the options in multiple passes? No not really in my opinion. Integrity Scan for example does a good check at what it's desinged to do in being a comprehensive dictionary validation checker but it is not a comprehensive data integrity checker. If you run it and get a clean bill of health, that is not a basis for deciding you don't need to Rebuild.
Below is my own personal essplanation of the options and when to run them. Read it if you dare @ThereseLogeais and I will try to respond in English. :)
----------------------------------------------------
Rebuild Key Files Information below is for Business Framework files only:
Rebuild:
To run Rebuild, don't click the Integrity Check or Optimize File checkboxes. It rebuilds similarly to how UFAR rebuilds but is more dictionary based and as a result less prone to select records for removal than UFAR (but if Rebuild doesn't work to repair the file, then UFAR is still an option make a backup of the file first). If no serious errors, Rebuild will also do a Key Compare of the before and after files.
Rebuild makes a copy of current file to a temporary file and rebuilds the temporary file. The current file is renamed to FILE+SessionID+.OLD. The rebuilt temporary file is then renamed to the current file name. Think of it as an ""implied Optimize"". If you Rebuild technically you don't need Optimize but sometimes Optimize has its own ""magic"".
Integrity Check:
Performs dictionary validation of each record and some read/write tests. If something is discovered, prompts you to run Rebuild (meaning don't click Integrity Check). It does a good job but only performs a limited number of bad data condition checks. Rebuild itself actually checks more and repairs bad data.
Optimize:
Reconstructs a data file by performing a Dictionary based READ of a record then WRITEs the record it to a temporary file. Process is repeated until all records complete. Then current file (the one READ from) is erased and temporary file (the one WRITTEN to) is renamed to be the current one.
Nice Side effects the reason why it's called ""Optimize"":
1.Empty space removed, file size may get decreased
2.New file written to new location on disk. In old days before modern hard drives and RAIDs were popular data file could've been sitting on
a ""bad spot"" on disk.
When do you run Optimize instead of Rebuild?
Bloated file (you've purged data but file size didn't reduce), need to reduce disk space to avoid encroaching 2GB size limit (prior to 4.40), or Rebuild didn't work (and not ready to try UFAR yet).