The current visual interdev 6 will only allow you to step through your asp code and will not for example launch vb's debugger, step through that and then go back to asp. .NET can do that.
Many problems of this type are related to the fact that asp passes variant datatypes, so if your com dll is not setup to receive a variant, you should cast the type with a "c" conversion function.
Example
asp calls a method in your com dll.
com function is declared like
public function Test(strPassed as string)
Your asp code should call the code like:
obj.Test(cstr("passing me"

)
same goes for "long" etc.
In short, check how your functions are declared and keep in mind that asp always passes variant data types.
Your best bet would be to use asp debugging and then if you suspect the problem is still in your com dll, then write a simple "test" program that calls the methods in your com dll. Gilbert M. Vanegas
Programmer Analyst III
County of San Bernardino - ISD
Email : gvanegas@isd.sbcounty.gov