>/ it will not use the deleted records as the new blank record... will
>you
>/ look at this code?
>/ thanks again...rob
>
>Well, it might need some modifications... since most of the lines were
>intended for debugging, I wrote a new one, which might work:
>>save_setdel=Set("Deleted")
>Set Deleted Off && make deleted records visible
>>loca for deleted()
>if found()
> recall
>* this really blanks the record, so it's like Append-ed Blank:
> blank
>else
> append blank
>endif
>Set Deleted &save_setdel
>thisform.grid1.column1.text1.setfocus
>
>Wow, this looks good, for a moment I almost wanted to use it myself.
>>On the other hand, it will keep getting slower and slower, once you run
>out of deleted records and the table gets real big, and... maybe you
>should check for existence of deleted records upon first time you open
>the table, or even keep a counter of deleted records, so you don't look
>for them if there are none. Another way round is to have a tag indexed
>on deleted(), but it seems like an overkill.
>Besides, I don't like writing apps where users go on deleting records
>every once in a while :)


Hi Dragan - I am doing it this way because it will always be a small table.
If this table was going to grow, I would use TABLE BUFFERING and there would
not be any blank or deleted records. what to you think? thanks ..rob