>>Hi,
>>
>>I have a feature in my app, scheduling procedure, where when user changes the schedule, the old records in a table have to be deleted and new added. In VFP version I was always "recycling" the records, that is "mark" them as "deleted" and then use them when new records have to be added. I am refactoring this procedure for SQL Server and consider doing away with "recycling". That is, delete records and let SQL Server "deal" with it. We are talking about deleting from 10 to 500 records (at the most) during the procedure. Should I still recycle in SQL Server or do away with this approach?
>>TIA
>
>I read through the replies and I agree with responses that Craig gave.
>
>I hate to sound dogmatic, but I'd recommend against trying to implement a recycling approach in SQL Server (partly because, as Craig said, there's no RECALL, but also because trying to invent your own scheme is not worth the effort)
Thank you. I am all for it; less code = fewer bugs.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
