Confirming what insertAlias said: ExecuteNonQuery returns number of rows affected, and in the case of your query, only the rows deleted from the last table.
Here are some recommendations, but you need to pull out SqlServer Books online and look this syntax up for yourself: allowing users to delete 50 tables en masse with a click of a web page is asking for trouble if you don't understand the syntax yourself:
1. Put the DELETE statement into a stored procedure. The web page will call only one stored procedure, which you can change as your database requirements change;
2. Your StoredProcedure (SP) can return a success or failure return value. It can return specific errors. It can decide whether to proceed, cancel or ROLLBACK if a table delete fails.
3. If you are just wiping out tables and do not care about ROLLBACK in case of failure, use TRUNCATE TABLE not DELETE, in order to efficiently not over use log files.
4. Within your SP, you can either hardcode your 50 TRUNCATE statements, which in your case you probably should do to avoid errors in using syntax you do not understand. This way you can also verify Foreign Key integrity. However, you could also write a cursor that gets all the table names from the system catalog (this catalog tables/views are different between SQL 2000 and 2005). You can either generate sql statements and execute them, or write a procedure that parameterizes the table names. There are plenty of examples of this on SQL websites. Here is a starter, but you can find scripts written by expert DBA's as well:
How to List All Tables
4a. You could, though not recommended, do the same on the server side code: execute a statement which retrieves the table names in question, then dynamically create the DELETE string. However, stored procedure would be the best practice.
5. If you use a cursor, you need to make sure you are deleting only the tables you want, not system tables, not other tables or databases. How are you handling concurrent users?
As far as backup/restore syntax, assuming your web user has permission to execute these statements, and that they are doing so in the "master" db and there are no connections to the database in question, then you can do this via a sql statement. Simply study and test the syntax for BACKUP and RESTORE:
Transact SQL 2000 BACKUP