This is a typical by-product of a server crash - data and table corruption. It does not matter that a VFP app was open but not being used. The fact that the tables were open at the time of the crash is enough to corrupt them. The best you can do is try to manually fix them or rely on a backup.

>Hi to all,
>I start a little application in a network. There's a computer which contains all the data that, while being used in other applications (Internet, or MS Word) crashed. It was necessary to turn it off.
>So happenened that the last set of data that was recorded (there were about six tables involved) was full of strange signs that I guessed were high value i.e. chr(255) (this term is from cobol language).
>Naturally there were no ways to append any other record to these tables. Seen that these happened already twice...Is there any simple way to prevent this problem ? Note that even though there was a PC using the VFP application, it wasn't used at that moment.
>
>Thanks
>Alessio