Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / General / September 2004



Tip: Looking for answers? Try searching our database.

Component problem reading registry

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rich - 30 Sep 2004 17:18 GMT
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.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.