I believe you. However, this happened to me twice in the past two weeks. Once when running an exe on a network and once when running in the development environment on my machine (different programs and different files). I just refreshed my runtimes and now the file used by the exe prg is apparently correct. The file in my development environment appears to still have the records appended to BOF but I do so many stange things in that environment that I can't say for sure. I have used Fox intensively since 1989 and I have never observed this type of behavior. Since the situation in the development environment is somewhat muddied let me just give you some more explanation of the problem in the other environment. It is a peer to peer Win95 network with 9 machines and and a dedicated server. I have a program called DOT that I use for maintenance. Basically it is a command interpreter. I went into that environment and typed: Use tasks . I then typed: Brow . Under these circumstances there should not be a controlling index. The file contains about 5000 records. The very first record was the one that I was looking for because it had disappeared from inside the exe prg. That was when I put out the message in the Thread. Like I said, I then refreshed my runtimes and now the record is where it is supposed to be. I don't know what is going on but I sure don't like it.

A problem is a problem only as long as it has a possible solution. Lacking that, it becomes a FACT!