On Fri, 22 Nov 2013 13:15:08 -0800 (PST),
forrest...@gmail.com
wrote:
Just to make sure ... are you saying that the problem is identical to
the OP's? The problem IS occurring at start-up of the VBIDE (vb6.exe)
and not the case where you have a "working" VBIDE (no errors during
development) that errors when you attempt to launch the DataView
Add-in?
Are you developing on a Windows 9x box?
Does this happen when launching any or a new project, or limited to a
specific project (.vbp)?
The answers may help to narrow down the "fix", but from a universal
point of view - this error is always caused by a "mismatch" component
(ocx, dll, ...). Or, in other words, whatever interface a program is
expecting is not matching up with the interface that is delivered by
whatever componnent it is being told to use to implement that
interface. The problem then becomes one of simply ferreting out the
specific interface/component. Then make sure the correct component is
available and registered.
If using Win98, Dr. Watson installed as your JIT debugger should help
provide a clue.
WinDebug is very helpful.
The most likely culprit is ADO or DAO. In this case just install the
latest and greatest MDAC and Jet libraries (if using Win98 make sure
you have installed DCOM as well). Make sure you only have one copy on
the box and all components are properly registered.
[Note:
1) Do not attempt to install MDAC/Jet on any Windows version past XP.
2) Do not waste time trying to select a specific version of the MDAC
or Jet installs. Just install the latest 'n greatest.
3) Make sure you have installed the latest VB and Control service
packs.
]