DEFINE CLASS visit AS custom OLEPUBLIC param1 = [] param2 = [] FUNCTION configure LPARAMETERS whatever1, whatever2 ...etc * store the params passed to properties, to be queried from outside WITH THIS * transform so we can easily show them in ASP .param1 = TRANSFORM(whatever1) .param2 = TRANSFORM(whatever2) ENDWITH * temporary return RETURN * balance of your code... ENDFUNC ENDDEFINEThen, in the asp, something like this to show the values passed in, from inside the COM object (remove extra spaces I added after the < ):
< HTML> < BODY> < % const g_sitename = "Sitename" const g_domainname = "MailDomain" const g_appdir = "ComponentDir" const Select_Departments = 0 const g_bodytag = _ "bgcolor=#ffffff leftmargin=0 topmargin=0 marginleft=0 margintop=0" DIM m_visit visit Function visit DIM strMessage IF IsEmpty(m_visit) Then Set m_visit = Server.CreateObject("govt2bus.visit") m_visit.configure g_sitename,g_domainname, _ "DRIVER=SQL Server;DATABASE=dbname;UID=Userid;PWD=password;SERVER=localhost", _ g_appdir Response.Write( m_visit.param1 + "< br>" ) Response.Write( m_visit.param2 + "< br>" ) END IF END Function %> < /BODY> < /HTML>This should allow you to see what the values were inside the COM object during the configure call. I haven't done enough VI work to suggest how to debug it there, but you can use this kind of approach to narrow down the problem and verify that what you're passing in is actually getting there.