>>>Researching an update problem. Just wondering if RECALL is the only way that a deleted record can become undeleted?
>>>
>>>Thanks
>>>
>>>Brenda
>
>>Brenda
>
>>RECALL is the only way to programmaticlly change the delete marker on a record in place. Now to explain the qualifiers in that sentence, 'programmatically' because a user may toggle the delete marker in either an edit or browse window or may use the recall dialog box or memu option, 'in place' because if COPY TO or SORT ON is used with SET DELETED OFF then the deleted records are copied but the delete marker is not. You may wonder why COPY TO is an issue, many times (especially in older code) in order to and gain some performance you will find tables reordered to match their primary index. To rearrange the table it was indexed and copied or sorted to a temp file, the original was then either zaped and appended from the temp file or erased and the temp file renamed to the original. This may seem like a lot of trouble, but when you learn to database on a 8086 with duel floppy drives you learn to take every advantage you can get.
>
>>Good Luck
>
>>Donny
>
>Ran a little example using SORT ON, and COPY TO. If 'SET DELETED ON', only the undeleted records were copied. If 'SET DELETED OFF', all records were copied, and deleted records were marked as deleted. I could not get these two commands to remove the deleted mark. Is there something I am missing?
>
>Brenda

Brenda

Looks like I'm the one that missed the changes to the rules, I did some checking myself on the versions I have loaded (just to make sure I'm not going senile). The behavior I described was what dBASEIII did, FPW 2.6 maintained the delete flag for COPY TO and SORT ON commands but lost it with an APPEND FROM and VFP (3.0 and 5.0) maintains the flag with the APPEND FROM command also.
Sorry to have misled you, I just wasn't expecting that old dog to learn any new tricks.

Donny