Another Observation limited to FPD25 a least is append from will undelete records. Recently I had a APPEND FROM (m.dbf) FOR !DELETED() and for some reasons stopped working. I have a lot of clients data which has the records came back from the phantom zone and am busy solving the problems.


>Not so much a question – more an observation that may help others avoid a difficult to find bug I recently encountered.
>
>When using APPEND FROM to add a set of records from table B to the end of table A, I found I was getting an incorrect set added. I had both tables open at the same time and the FOR condition applied to table B as a BROWSE achieved the correct subset of results. However, when applying the FOR condition to the APPEND FROM a different set of results was being passed across to table A.
>
>I discovered that the APPEND FROM will always search for table B along the default path. APPEND FROM ignored the fact that I already had the intended table B open. I had an old version of table B higher up the search path than the one currently open and this one had spurious records some of which met the FOR criteria and were being added to table A.
>
>You can avoid this trap by specifying the full path to table B or making sure that you only have a single instance of the file in the search path (which most folk will!).
>
>Barry