MDAC often fouls up the DAO reference in Access applications, without
marking it as MISSING: (which is normally what happens when the references
get mucked up) Normally, just unselecting, backing out, then going back in
and reselecting the DAO reference is sufficient to fix any problems.
HTH
--
Doug Steele, Microsoft Access MVP
Beer, Wine and Database Programming. What could be better?
Visit "Doug Steele's Beer and Programming Emporium"
http://I.Am/DougSteele/
Quote:
> I recently loaded mdac 4 containing jet 4.0 and I thought it will not
> conflict with jet 3.51. However when I ran my old project with reference
to
> jet 3.51, it is giving me an error of "object variable or with object
> variable not set.". When I changed to reference to 3.51, the error went
> away. What Am I doing wrong?
> I cannot convert to jet 4.0 because the project is using Access 2.0.
> Thanks in advance.....
> --
> Tony Palag
Jet 3.51 vs JET 4.0