> Did the crash bring down the VFP host? Just the DLL crashed, and is now sitting in an undetermined state in memory?

Hi Mike,
Judging from the replys I got, I may be going about this the wrong way. I'm a longtime VFP developer new to web programming. I have a small VFP program that reads an Oracle database and writes an ASCII file. It connects to Oracle via ODBC, runs several SELECT statements, writes a text file, then exits. Now that I've tested the program in-house, I want to make that program available to all the branch offices of my company. My idea was to make it into a MTDLL, then call it from an ASP page running on my company web site under IIS 5.0.
In my first pass at this, I broke the program into 3 methods for easier testing, and call it like this from the ASP page:

set objLoan = Server.CreateObject("loan.loan")
objLoan.CreateCursor()
objLoan.InitRec()
objLoan.WriteFile()
set objLoan = nothing

Do I have the right concept here?
I had an undefinded variable in my InitRec method, and the ASP page returned an error. So I tabbed back to VFP 7 and fixed my error. When I tried to rebuild the DLL, and got a "file access denied" error. Do I need to start/stop IIS to get the DLL released? What would you do in a real-world situation if your DLL crashed on a web server running many other sites?
Thanks,
John