NOTE: Even if you can create a DLL, I will still expect active participation in the Discussion topic. It deals with testing the code as a Standard EXE. WARNING: Be prepared to restart your webserver many, many times! Every time you want to re-compile your DLL, you will have to restart the webserver in order to release it's hold on it! The first step is to create the DLL.  Click on "File" then "Make x.dll" where x represents the name you gave your project. This step is where you will discover compile-time errors. If there is an error, VB will usually give a message, and will sometimes highlight the section of code that caused the problem. Try and figure out the error yourself, or use the Disucssion/Bulletin Boards as resources. I will be montoring the Disucssions. If this is completed successfully, you will see a file in you directory with a DLL extension.  The second step is to register the DLL. Click on "Start" in your task bar. Click on "Run" Click on the "Browse" button Browse for the "regsvr32" program. It is located in the "system32" folder of your windows (winnt) directory. Click on "Open" DO NOT click on the "OK" button yet! After the name of the regsrv32 program, you need to type in the full path and name of your DLL. The full path and name must be in quotes. See example below. Now click the "OK" button You will get a message indicating whether or not the DLL was registered successfully. To register my DLL, the white box in the Run dialog window contained the following:  Although, I use a simpler process. I've registered the regsrv32 program is the one to open DLL files. This way, I just double-click the DLL in Windows Explorer to register it. You can do this, too: Locate the DLL using Windows Explorer Double-click the DLL A window titled "Open With" will appear Click on the "Other..." button Browse for regsrv32 in the "system32" folder of your windows (winnt) directory Click "Open" Check the box next to "Always use this program...." Click "OK" The third step is to navigate your pages just the same as you did before. Finally, you may choose to write and test one function at a time. Which means you will be re-compling the DLL. The problem is, once you've opened an ASP page that uses your DLL, the webserver keeps a lock on it. To release the lock, you need to stop the Admin Services.  c:\winnt\system32\regsrv32.exe "D:\My Documents\Projects\SCCC\Courses\SP02\CIS237\CIS237.dll"  For Win98 and PWS: Right-click on the PWS icon in your system tray Click on "Stop Service" from the list Right-click on the PWS icon in your system tray Click on "Start Service" from the list For Win2K: Open "Control Panel" Open "Administrative Tools" Double-Click on "Services" Scroll through the list and click once on "IIS Admin Service" Click on "Restart Service" in the toolbar (a square with a right-pointing triangle) You will be asked if you also want to restart "World Wide Web Publishing Service," and possibly "FTP Publishing Service." Say "Yes."  You may want to be able to test using interpreted mode, instead of compiling. This is useful for locating logical errors in your program, if you are getting unexpected results. You can do this by NOT creating the DLL, but simply running the program. The "DLL" will exist as long as the program is running.