C++/VB - VB6 + ADODB.Recordset + Vista = Automation error -2147024769

Asked By timm

10-Dec-08 03:34 AM

Hello everybody!

WEEKS have passed now and it won't come to an end.

The problem is simple:

I've got a VB6 program that runs wonderful under Windows XP but Vista always
hangs up, when it tries to execute the following command:

Set rs = New ADODB.Recordset <-- DOESN'T WORK!

This command exists inside a function, at the top of the .bas-File, the
Variable is declared:

Public rs As ADODB.Recordset

___________________________________
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
I've also tried to start with a new (clean) project and made everything as
simple as possible. It seems that no ADO-Components work under Windows Vista.

A try to get the ADODC-Control to work also failed (worked under XP, but not
under Vista).

___________________________________
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
I posted in several forums now, but nobody could help me.
Maybe the answers of others could, so I will link some of my Threads:

1) http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4164774&SiteID=1
2)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4219413&SiteID=1&mode=1
3) http://www.vbarchiv.net/forum/id13_i16850t16850.html
4) http://www.dbforums.com/showthread.php?t=1635645

10-Dec-08 03:43 AM

I want to add the following: I am _NOT_ trying to connect to any database, I
just need the Recordset for a "List & Label"-Function!

10-Dec-08 04:32 AM

timmi <timmi@>'s wild thoughts were
released on Wed, 10 Dec 2008 00:34:01 -0800 bearing the
following fruit:


I do this this all the time in all the products I work on
and have never encountered a problem with Vista.

It's seems to me it's more likely a problem with your
installation of ADO.




--
Jan Hyde (VB MVP)

https://mvp.support.microsoft.com/profile/Jan.Hyde

10-Dec-08 04:42 AM

But I tested it on 3 Vista Systems now.

1 manual clean Installation (Business) and
2 different Laptop OEM Versions (Toshiba & Asus), which were pre-installed...

I haven't changed something, concerning the ADO-Installation (WDAC/MDAC).

10-Dec-08 08:09 AM

¤ Hello everybody!
¤
¤ WEEKS have passed now and it won't come to an end.
¤
¤ The problem is simple:
¤
¤ I've got a VB6 program that runs wonderful under Windows XP but Vista always
¤ hangs up, when it tries to execute the following command:
¤
¤ Set rs = New ADODB.Recordset <-- DOESN'T WORK!
¤
¤ This command exists inside a function, at the top of the .bas-File, the
¤ Variable is declared:
¤
¤ Public rs As ADODB.Recordset
¤
¤ ___________________________________
¤ ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
¤ I've also tried to start with a new (clean) project and made everything as
¤ simple as possible. It seems that no ADO-Components work under Windows Vista.
¤
¤ A try to get the ADODC-Control to work also failed (worked under XP, but not
¤ under Vista).

Are you running this under the development environment in Vista or is it after your application has
been deployed to Vista?

I would make certain that you have distributed all of the necessary files with your application.
Sometimes missing libraries can cause strange exceptions to be generated. The error text that is
associated with this error number "The specified procedure could not be found" doesn't really make
sense in this context.


Paul
~~~~
Microsoft MVP (Visual Basic)

10-Dec-08 08:21 AM

I think I can see a light at the end of the tunnel!

It seems that the Installation-Process of the Tool is the guilty part.

Before the installation, a simple ADODB.Recordset-Test was running, after
the installation, the -214... automation error of the same example pops up.

I think the Installshield-Setup installs/copies/registers his "own"
ADO-DLL's or something.

After an uninstall of the program, a runtime error 429 appears...

So, the installation "destroys" something, think we have to rebuild the setup!


Greets

timmi

10-Dec-08 08:30 AM

In this case, it IS the problem, that "all of the necessary files" were
distributed with this application.

See my post above. Thanks for your hint! :-)

10-Dec-08 08:56 AM

I also code VB apps using ADO all the time and never have problems with
Vista. However, when you install anything on Vista, it must be Vista aware
or it most likely will fail. I had to upgrade InstallShield to a version
that recognizes Vista. When I install with a setup program I try to always
use "Run as Administrator". On Vista it does not matter if you are logged in
as Administrator, you must use "Run as Administrator" (right click the *.exe
and select "Run as Administrator").

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--

10-Dec-08 12:33 PM

up.
setup!

It may help to note that you can not and should not install any ADO, OLE DB,
or OLE components (MDAC) on a Vista machine. Vista comes with these
components already installed as the DAC v6.

Normally, an install will report an error or simply be ignore if it attempts
to do so. However, with Vista's "compatiblity mode" - Nevermind, I'll
restrain from inserting a personal opinion on this feature.

Remove all attempts to install these components from your install package.

You should include msadodc.ocx

Take a good look at the list of supported, shipped, and non-shipped
components given here:
http://msdn.microsoft.com/en-us/vbrun/ms788708.aspx
And modify your install accordingly.

While less practical for a Shrink-wrap package, I have found it useful to
place the "Supported Runtime Files to Distribute with Your Application" in
their own install and manage them separately when updating a new Vista box
within an enterprise, or friends and families environment. Simplifies
trouble-shooting.

-ralph