-
May 17th, 2019, 08:24 AM
#1
Thread Starter
Fanatic Member
-
May 17th, 2019, 08:29 AM
#2
Re: Visual Component Manager
I never use the old VCM myself.
The Data View is useful for working with databases and even tabular text files via Jet 4.0 though:
-
May 17th, 2019, 08:36 AM
#3
Thread Starter
Fanatic Member
Re: Visual Component Manager
Thanks for the reply. I finally gave up and did a re-install of VB6 and the problem went away.
Edit: Thought I had it fixed with the reinstall. But the problem came back. I unchecked the Visual Component Manager. So far it seems to run. But do I need that?!?! Seems like my problem may run deeper. Thinking something to do with MDAC...
Last edited by Darkbob; May 17th, 2019 at 08:50 AM.
-
May 17th, 2019, 09:10 AM
#4
Re: Visual Component Manager
MDAC/DAC has been preinstalled and serviced through Windows Update for quite a long time, even on long-dead Windows XP.
It seems more likely there is something else going on like a GUID conflict. Maybe somebody else has a solution. All I can think of is to dig through the VS/VB 6.0 CDs to search for possible supplementary information.
-
May 17th, 2019, 09:17 AM
#5
Re: Visual Component Manager
This article is no longer online but here is a link to an archived copy:
https://jeffpar.github.io/kbarchive/kb/191/Q191791/
You can also search your MSDN CDs for Q191791 there. I don't know if anything there will help with this issue though. VCM was always a little flaky. I haven't installed it in decades.
-
May 17th, 2019, 09:24 AM
#6
Thread Starter
Fanatic Member
Re: Visual Component Manager
Sounds like something I don't need. It's gone and so are my problem. Thanks!
-
May 20th, 2019, 05:37 PM
#7
Member
Re: [RESOLVED] Visual Component Manager
I started getting this error when using VB6 on Windows 10. I'd like a fix if anyone knows one. It runs fine after that message, so its just an annoyance.
Windows 10 v1809, VB6 SP6, NO MSDN
-
May 20th, 2019, 05:47 PM
#8
Fanatic Member
Re: [RESOLVED] Visual Component Manager
Originally Posted by PsuFan
I started getting this error when using VB6 on Windows 10. I'd like a fix if anyone knows one. It runs fine after that message, so its just an annoyance.
Windows 10 v1809, VB6 SP6, NO MSDN
Here is what I have installed, but on Windows 7. I don't normally have Visual Component Manager Addin loaded, but after testing it, it seems to work fine.
-
May 20th, 2019, 05:55 PM
#9
Member
Re: [RESOLVED] Visual Component Manager
Must load by default, because I have it loading as well. That and the MouseWheelFix...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|