you missed what i said, handle EVERYTHING in the dll, and return the OUTPUT not the asp code, the HTML OUTPUT.
then just response.write out the dll call
example .. in dll
function hello()
hello = "hello"
end function
----------------
in asp:
set mydll = createobject("mydll.whatever")
response.write mydll.hello
set mydll = nothing
cant see HOW hello in the output page came to be, it's just there
so ... in turn :
example .. in dll
function hello(ARGS)
hello = Execute(decrypt(dbcall(sql & ARGS)))
' you JUST cant response.write in the code, the DB code will NEED to be VB code NOT VBS
end function
----------------
in asp:
set mydll = createobject("mydll.whatever")
response.write mydll.hello(ARGS)
set mydll = nothing
and voila, html output, all someone knows it's from a DLL that is IF they can get the sourcecode from your ASP page to beginwith... then again if they have access to your ASP sourcecode, they PROBABLY can get the DLL file, and or access to your DB
![[thumbsup2] [thumbsup2] [thumbsup2]](/data/assets/smilies/thumbsup2.gif)
DreX
aKa - Robert