>I don't believe it can be the newtwork. Considering the other weird bug you have, I would say that something's wrong with the computer (the CPU or the memory).
>
>In both problems, it looks like the CPU executes a command before the previous one ends, or, it skips lines of code.
>
>If the problem appears on only one computer, try to see what happens if you use it with the cover off. If it's an overheated CPU, this may help to cool it down and to make it work. Look also at the CPU fan... Overheated CPUs have really weird behaviors. Sometimes, a system may work for weeks before noticing the overheat problem.

It may have been noticed I was absent last week of April (everyone was greatly relieved ;), and I'm still not sure of the cause: my machine started misbehaving in some interesting ways. Reinstalling everything simply didn't work - done it several times, and there was always some error during installation, even after formatting the C: partition. Some mass copies I've done before this formatting proved later to have some 16 or 32 bytes faulty (and guess what - this was discovered in VFP.exe). The thing which solved it so far is two things... a heavy-duty cooling fan ("you sure need it, if your machine works all day"), and turning off the external cache. Didn't notice any speed degradation, and, besides, losing a week's time far outweighs any speed issue.