>Hi Peter,
>
>I wrestled with these issues late last year, and by chance I came across Gareth's KB article which reported the 'problem' that if records were added to a corrupted file (header count error), no error was reported. It is now classified as a 'bug'.

Geoff, at least I found the thread you are implying (Thread #580276) and I got the message from it. BUT :

Let's say I followed the discussion with Vlad, and stopped there assuming that's the basis for the remainder of the thread. I can say : this part of the thread sounds like "rubbish" to me, I can't recognize it at all, and therefore my idea about it : it's just not true (at all).

To be on some safe side : I've been around with Vlad for a couple of hundred emails and more, and in fact I can't believe that I won't believe him. So maybe I just misunderstood it all. But anyway :

Assumed that the message was that the table header isn't updated when someone performs an Append Blank -> bull. If that were the case (for the sake of logic), Fox wouldn't work at all.

I guess "you" are all looking at this from some complete wrong direction. I mean, yes, if PC1 adds a record, and PC2 performs a Reccount(), is indeed doesn't show the proper count. But don't get bothered by this, and don't get mislead by it ! It just needs the proper command to enforce the re-read of the server, as (for example) the Append Blank does this itself internally.

Again, without this nothing would work.
It doesn't need a Flush and it doesn't need a Close data or whatever, which btw doesn't even help !! (test it !). The PC appending just updates the header info, and it's only the "skill" to find out at the other PC. But skip it, because Fox does it for you.

By no means I am saying that header corruption doesn't exist or is foolproof. The only thing I say is that the discussion with Vlad doesn't touch reality.

But yes, I have this corruption problem, so read all of the above as if I whisper it ...