Well everyone....it looks like I solved the RDO 429 error on our system here
but it was certainly not a likely workaround...but it was not too painful,
I simply ran the VB 6.0 setup and chose to only install the data access
components. The only downside was I had to recreate all of my dsn's in my
ODBC setup...(had a backup anyway). So that's the scoop! It worked for me.
Good plan if your need to keep your app in VB 5.0 and use RDO.
> Could this have anything to do with RDO does not install properly on
> machines that do not have ODBC installed first? Just a guess, I recall
> to be an issue somewhere but can not recall the details.
> > Mitch,
> > I experienced the same problem here. I ran the MS fix as found on
> > Knowledge base but it did not work...in fact, it made things worse. I
> > ultimately fixed it by (believe it or not) installing VB 6.0! After
> > this...everything worked fine. The one mystery left unsolved is why the
> > worked fine on the dev machine with VB 5.0 SP3?????
> > Mike (Spike) Desjardins
> > Technical Sales Engineer, ASD
> > Pronexus Inc.
> > an Active Voice company
> > http://www.pronexus.com
> > > There is apparently a known issue with VB5 SP3 and RDO wherein the
> > > reference to RDO in an app causes Error 429 "Cannot create Active X
> > object".
> > > I don't know the issue number, but it's on the MS Knowledge base.
> > > Anyway, if you download the fix, it solves the error on the
> > > machine but the error still occurs on the clients. I'm not why this
> > > because we are sure to re-package/re-compile the application after the
> > > has been installed.
> > > Please, if anyone knows a workaround (other than installing VB5 on all
> > > clients...EEK!), let me know.