[continueing]

Though far to difficult to explain, I know had quite another base for the remainder of the problem : the browse showing corrupted data for more records above it. In addition, it was a pure coincidence that some employee just yesterday recovered from the thing happening yesterday by some wrong means, by which he coincidentally fixed the thing in the first record the browse showed as corrupted. This imlied the corruption to be fixed in the physical file right from the beginning where the browse so strangely can show it and what it showed was quite another experience, also too stupid not to have found before :

The exact beginning of the block. So in the end this leaves us with the so simple fact of just one whole block being corrupted. I'll summarize this at the highest level in this thread.

Some conclusion of mine in here :
How UT can help whereas nobody can point the problem out really.
Over two years far off, and in three days so near.
Thanks for now !!