>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

SQL recycle delete data space to write new data.
VFP doesn't do this operation and then a dbf garbage collection
require exclusive access and a copy of the dbf file.

My suggestion is not to use this
approach in SQL Server. Complicates and slows down all operations,
and especially it increases the likelihood of errors.