You might not need to do a backup/restore. Using SQL Server transactions allows you to commit/rollback the results of batch processes.


>I need to have my VFP 6.0 code create a back up of a SQLServer7.0 database before doing some batch processing on the tables. I would also like to give the VFP code the option of restoring the database if the batch process hicups.
>
>What's the suggested 'best practice' for this.
>
>Note: The VFP code is run by various users (i.e. their network logins are different. Also, none of the users are database admins or dbo owners.) I do not have control of the server. It is in a separate department so getting or changing permissions and access rights is sort of a problem. All this might have some bearing on how best to do the backup/restore.)