I've had this happen before, when SQL was stopped to delete the log file you got as much of a commit as it possible, usually the log file has committed all transactions and if it hasn't there isn't much you can do.
The fastest way to bring the database back online in this situation is:
1. Stop SQL and rename the mdf file
2. Restart SQL and delete suspect database (possibly have to restart SQL)
3. Rename the mdf to it's original name
4. Use sp_attach_single_file_db to bring
5. Do a full backup.
The next step is to take a baseball bat to the fingers of the sysadmin who did this so they will remember to call the DBA next time.