Ross,
Are you trying to make the development server take the physical place of the production server, or just temporary host the database until the production server can be brought back on line?
To get the database restored to the development server, recreate the database on the development server just as it was on the production server. The easiest way to do that is to run sp_help_revdatabase on the database. This system stored procedure will create a script that will re-create the database in the same fragments (sequence and size) as the original. This is very important! You'll have to create the devices first. If you don't use the same device names as on the production server, change the script to use the names of the new devices. Then restore the database from tape.
At this point, all clients should be able to connect to the development server and continue working by reconfiguring the workstations to use the development server instead of the production server. It might be as easy as changing the DSN.
If you don't want to change the workstations, you'll have to make the development server look like the production server. Take the production server offline (if it's not already). Change the development server's`NETBIOS name to that of the production server. I think you'll have to reboot. Log onto SQL Server and use the sp_dropserver system stored procedure to drop the development server name. Then use sp_addserver to rename the development server to the name of the production server. You have to use the LOCAL parameter to tell SQL Server that you're renaming the local server:
EXECUTE sp_addserver new_name, LOCAL
Stop and restart SQL Server and everything should work.
If you're identifying the target server by and IP address, you'll have to change the development server IP to that of the production server.
BTW, this is basically the same process for a SQL Server 7.0 except that after changing the NETBIOS name, rerun SQL Server setup and choose upgrade. SETUP will correct the necessary registry entries.
-Mike
