I've had a VB6 COM component running in an ASP environment without
problem for a couple of years. It gets its database connection
information from the registry via the VB GetSetting function.
I now have another need for a similar component. Using the exact same
code, I have been unable to get it to successfully read the registry.
After running RegMon and comparing the two scenarios, the only
difference I can find is that the first is executing an "OpenKey"
call, and the second is making a "QueryValue" call. I'm assuming that
this is my problem.
Any ideas why the same "GetSetting" function would result in a
different call to the registry? Is there anything that can be done to
control it? Should I just scrap GetSetting and use the Windows API
directly?
Thanks.
Veign - 30 Sep 2004 17:42 GMT
Here is a full registry component that would make accessing the registry
through the API:
Registry Component:
http://www.vbaccelerator.com/home/VB/Code/Libraries/Registry_and_Ini_Files/Compl
ete_Registry_Control/article.asp

Signature
Chris Hanscom
MVP (Visual Basic)
http://www.veign.com
--
> I've had a VB6 COM component running in an ASP environment without
> problem for a couple of years. It gets its database connection
[quoted text clipped - 13 lines]
>
> Thanks.