Re: Windows XP SP2 MDAC 2.8 SP1

From: Thomas (Thomas_at_discussions.microsoft.com)
Date: 02/21/05 

Date: Mon, 21 Feb 2005 06:35:08 -0800

Not to my knowledge. Here is a link that displays the MDAC release history.

http://support.microsoft.com/default.aspx?scid=kb;en-us;231943

Tom

"manish_agarwal@adp.com" wrote:

> Hi,
>
> Is MDAC 2.8 SP1 available for download now.
>
> Thanks
> -- Manish
>
>
>
> Val Mazur wrote:
> > You could be in trouble in this case. MDAC 2.8 SP1 will be for
> download for
> > sure, but since there is no official announcement about it, it is
> hard to
> > say when it could be released. Say was with MDAC 2.8, when it was
> initially
> > released only with Windows 2003. I will try figure out what are
> possible
> > solutions in this case and will post it here
> >
> > --
> > Val Mazur
> > Microsoft MVP
> >
> >
> > "Thomas" <Thomas@discussions.microsoft.com> wrote in message
> > news:1F08919C-5385-43BE-B94D-8CDB1192B298@microsoft.com...
> > > Hi,
> > >
> > > I installed MDAC 2.7 on the server; but the error '~' of Object '~'
>
> > > Failed"
> > > still occurs; but is not a reproducable error. I guess my next step
> is to
> > > insure that the application components (VB6) are compiled updated
> with the
> > > same MDAC version that is running on the server. My question now
> is; since
> > > my
> > > development machine now has XP SP2 which contains MDAC 2.8 SP1; for
> which
> > > there is now web release with which to update the server; what
> should I
> > > do?
> > > Any thoughts would be much appreciated.
> > >
> > > Thanks
> > > Tom
> > >
> > >
> > > "Val Mazur" wrote:
> > >
> > >> Hi,
> > >>
> > >> Usually this error means that MDAC installation was corrupted. In
> a case
> > >> if
> > >> your application was compiled to use MDAC 2.8 and you try to use
> it on a
> > >> platform that has MDAC 2.6 it might fail with this error. But if
> error is
> > >> not consistent and ADO code works fine in some cases, then I would
>
> > >> suspect
> > >> that it is not a version-related issue, but actual corrupted MDAC.
> > >>
> > >> --
> > >> Val Mazur
> > >> Microsoft MVP
> > >>
> > >>
> > >> "Thomas" <Thomas@discussions.microsoft.com> wrote in message
> > >> news:1DDE1DAD-8D81-48CC-BACB-CEACAE09AA49@microsoft.com...
> > >> >I recently updated my development computer to Windows XP SP2.
> Unawares,
> > >> >i
> > >> >now
> > >> > realize that a new update for MDAC came along with. My VB6
> project
> > >> > produces
> > >> > DLL's targeted for a Windows 2000 server currently running MDAC
> 2.6.
> > >> >
> > >> > Currently on the windows 2000 server we are experiencing
> periodic
> > >> > failures
> > >> > that render an evelt log message of '~' of Object '~' Failed"
> message.
> > >> >
> > >> > It is unclear whether I should return to an ealrier version of
> MDAC of
> > >> > my
> > >> > dveelopment computer or install MDAC 2.8 on the server.
> > >> >
> > >> > Does anyone have any thoughts.
> > >> >
> > >> > Tom
> > >> >
> > >>
> > >>
> > >>
>
>

Relevant Pages

  • Re: VB6 Questions
    ... "Krishna Prabhu" wrote in message ... > I also have confirmed that MDAC is installed successfuly. ... > "Val Mazur" wrote: ... You could download it ...
    (microsoft.public.vb.database.ado)
  • Re: Application Error 1000
    ... MDAC to see if it is fine or not. ... > "Val Mazur" wrote: ... >> that since you application uses DSN, ADO will use OLEDB for ODBC between ... >>> is written to the log file. ...
    (microsoft.public.vb.database.ado)
  • Re: W2K to XP ADOX 2.5/2.8 problem
    ... Did not you install any third-party components, ... upgrade MDAC? ... "Juan Ciervo" wrote in message ... >>> Val Mazur ...
    (microsoft.public.vb.database.ado)
  • Re: Installing MDAC 2.7 and JET 4.0
    ... MSDN. ... >>> a Component Checker to see if MDAC is OK or not. ... >>> Val Mazur ... >>> Microsoft MVP ...
    (microsoft.public.vb.database.ado)
  • Re: Recordset gets corrupted
    ... "prash" wrote in message ... > is there any paramter that i have to set to get the record set unicode ... > "Val Mazur" wrote in message ... I think you need to install localizable copy of MDAC to work ...
    (microsoft.public.vb.database.ado)