I am under the impression that you cannot develop applications using ado 2.5
and be able to distribute to  machines using win 95 or win  98.  Article
Q259379 seems to require  that you are forced to continue using ado 2.1
beacause the msado15.dll file cannot be run on systems  below win 2000.

Wow, is this possibly correct?  Why can't the dll file be installed to the
user machine?  Is there a way to do this?

If this is the case and I change back  to the ado 2.1 library - can i use
the ado 2.5 recordset library in connection with the 2.1 library?

I think you may have misunderstood; the article is stating that developers
on Windows 2000 cannot use msado15.dll versions earlier than ADO 2.5,
because it's a protected operating system component. Thus, you can't
"backgrade" to 2.1 to target older operating systems that may have that
version installed.

If you're developing on Windows 2000 or later, you must upgrade users of
your application to MDAC 2.5; Win 95 and Win 98 both support MDAC 2.5
(although they do require DCOM98 be installed first).

You cannot mix versions of the different ADO libraries; they need to be
updated together, using the mdac_typ.exe redistributable. Just include the
2.5 version (or whatever version you're developing with, available at
http://www.microsoft.com/data) in your installation package, and make sure
it is run (not just copied) on the target machine. Package & Deployment
Wizard knows to do this if the file is included in your package.

Hope this clears up any confusion!

Steven Bras, MCSD
Microsoft Developer Support/Visual Basic WebData
This posting is provided AS IS with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.

Steven,

Thanks for the reply and yes it may have helped clear the cobwebs; however, just to make sure..

Are you  saying if I am developing on a Win 95 and Win 98 machines with VB6, SP5, referencing ado 2.5 and ado recordset objects 2.5 the PD should automatically install the appropriate mdac on the user  machine (dcom present of course), or do I need also download something else in addition to have installed SP5?

If you only want to answer the above question - thanks, however, if your feeling  particularly charitable read on.

My facts  are, I am developing on Win 95 and Win 98 machines with SP5 of VB installed.  SP5, as you no doubt are aware, provides an upgrade possibility of ado 2.5, so I changed to that reference and went blissfully on my way.
Things progressed  nicely for several months, or I think it has, until I received a call from customer regarding a Error 430 message, i.e., "Class does not support automation or does not  support expected interface".  Checking my KB it seemed that Q259379 was the most likely culprit as it
seems to occur at the point a recordset is opened.  If  that is not the problem, I am befuddled as to which direction  to proceed to determine cause.  Their machine is NT but other machines with same OS seem to install
OK so I thought maybe those machines had ado 2.5 from elsewhere.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

The PDW automatically includes the version of mdac_typ.exe from
%systemroot%\program files\microsoft visual
studio\VB98\Wizards\PDWizard\Redist. I'm not sure that MDAC updates update
this copy as well, so make sure your copy there is late enough to contain
the library you're using (2.5 or later). If you're not sure, download
specific versions from http://www.microsoft.com/data.

Regarding you 2nd question, it's likely that you did indeed deploy an older
version of the msado15.dll, and that your code expects the 2.5 interface. I
would start by checking the version of msado15.dll on those machines and
comparing it to your development machine, where the code works as expected.

Hope this helps!

Steven Bras, MCSD
Microsoft Developer Support/Visual Basic WebData
This posting is provided AS IS with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.