>I'm not using databases, just straight free tables. I was previously using a database, but due to some complications had to switch back to straight tables. The cursors are just selects and aren't buffered, neither are the tables (I didn't put any code in to in anyway buffer them). When the program crashes, it leaves 4 .tmp files and one .cdx file in my temp directory. One of the .tmp files has environmental info, all garbled, but table names from this and other projects. The other has a long string of table names, equally garbled. All the others are blank. One of the files was 13k, but had no data in it and no, it wasn't the same size as the table that gets wiped. I've gotten the error to happen on navigating around in the form (while I had to DOHISTORY logging. the log file apparently was never created) but all other times it is caused by the closing of the form. Could I somehow have buffering on in some form even though I'm not using databases? The tables were previously bound to the
>database. I have several other sets of data going back quite some time and they all give me the same trouble...
>

It's quite likely, in fact - if you haven't specifically set the default mode, I think VFP 3 defaulted to optimistic record locking on views and no buffering on tables, unless you overrode them in the form's DE or issued CURSORSETPROP() to change the mode; if you've subclassed your base form, you may have inherited a different default buffer mode without knowing it.

Ordinarily, I'd expect to see dialog boxes from VFP if you have buffered changes stacked up and you go to close the table or view (error 1545, 1585 and 1595)

>Cole