Not sure exactly what you are trying to do.
But I took a few minutes and came up with...
In VB
Project1 is a project that references your dll project
it has a form with a command button as follows.
Private Sub Command1_Click()
Dim objMyReport As myReport
Set objMyReport = New myReport
MsgBox objMyReport.ExportSpecs.HeaderFormat
End Sub
Here is your activex dll project called WEBDLL with 2 class modules.
MyReport is the "base class" that can contain a class called ExportSpecs and the class is returned as a property so...
(Class MYReport)
Public Property Get ExportSpecs() As ExportSpecs
Set ExportSpecs = New ExportSpecs
End Property
ExportSpecs has a property called HeaderFormat (lets say it returns a string in this example).
(Class ExportSpecs)
Public Property Get HeaderFormat() As String
HeaderFormat = "Hello World"
End Property
That worked fine in visual basic from a form calling the activex dll.
Now in your web environment you would compile the activeX dll and make sure its registered on the web server.
IF YOU WANTED INTELLISENSE ON THIS DLL I believe you would set the reference to the dll from your interdev project.
(Project->ProjectReferences) and select your compiled and registered dll.
Here is an explanation of Project->ProjectReferences from the visual interdev help.
"Use this dialog box to choose the type libraries used for statement completion in the HTML Editor and Code Editors. Type libraries contain the properties, methods, and events for controls and other objects installed on your machine."
That seems to work for me. Or dont worry about the intellisense and simply code it as follows...
Your asp code would look something like...
dim objMyReport
set objMyReport = Server.CreateObject("WEBDLL.MyReport"

response.write objMyReport.ExportSpecs.HeaderFormat
That should work also...
Gilbert M. Vanegas
Programmer Analyst III
County of San Bernardino - ISD
Email : gvanegas@isd.sbcounty.gov