Jim,

>>You reported a bug that reindex no longer removed CDX bloat. I proved your bug report to be incorrect, reindex always has removed CDX bloat.
>
>You did nothing of the sort!

Rows 7 & 8 in the table of the Wiki article, directly refute your bug report. http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,15,652071

>Your promised second report (quoting "Since the code below does not do any record insertions this analysis does not cover the secondary type of bloat. That will be covered by another set of test code posted in the near future." never did materialize

The event in my family life that causes the link to the grid.org cancer research project to be included in my signature block prevented me from returning to the topic of CDX internals. By all means, if you are still interested in the topic go ahead and do the research and post it.

>My my my, how a story changes over time!!!

It does Jim, you seem to be now reversing the agreement you had in this message http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,15,653417

>You were quite pleased with the rationalization for the doubling of the CDX size put forward by ChristofL at the time and happily accepted that it was all by design and to fix a/some bugs. It was all hypothesis and guessing and turned out top be a full crock of crap yet you persist with this double-speak!

I acknowledged the doubling of size to be a bug. I also stated in the threads here that there are some positive benefits to changing the way B+Tree nodes split. Ulitmately though VFP is much more adversely affected by a doubling of size of the CDX for large tables and it was changed. I wish that a new setting had been added to the language so that we could control this on a table by table basis to help us optimize our databases.

Frankly I trust Christof's investigative research into the issue much more than I believe the "explanation" you offer in the Wiki article. Quoting you: I'll offer mine... when making changes that can affect TAG manipulation/accuracy the VFP Team facilitates its debugging by removing the 'compression' normally done so that they can better see the full story when needed. They simply forgot to turn on the compression again in VFP7SP1 once their TAG testing was finished. Sounds as plausible as any to me.

>No, I feel that the incident effectively stopped further 'persecution' of myself.

Or perhaps it just means that I've not seen you make any invalid bug reports of late. I'm an equal opportunity debunker.

>That FabioL has contributed SEVERAL legitimate bug reports also makes no difference. You intend to shut him up and you will contine until that happens.

Please point me to any criticisms I've made to any of his valid bug reports.

>The operation was exposed with my indicent and it is now following exactly the same script as regards FabioL. But I suspect that his skin is thick enough to resist it too.
>
>Summarizing: I feel I survived the persecution and no longer feel any. You (the gang) have moved on to FabioL as I see it.

You are just too paranoid. If I see something posted, by anyone, that is seriously flawed I will reply as I see appropriate.