Type mismatch - CurrentDb

[Steve B.]

http://www.microsoft.com/communitie...ding&mid=c36295fd-5021-4874-ab51-9fd412086eef

 

['69 Camaro]

http://www.microsoft.com/communitie...ding&mid=c36295fd-5021-4874-ab51-9fd412086eef

Try:

http://www.access.qbuilt.com/html/ado_and_dao.html

http://groups.google.com/groups?as_...81&as_maxd=28&as_maxm=3&as_maxy=2007&safe=off

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


news:[email protected]...

 

[Steve B.]

Thank you for helpful post.

I think the problem was fixed by referencing the DAO.Database and possibily
moving the DAO referencing above ADO (not sure).
Now we have another problem on some machines with error #429 which I will
post seperately after doing some research
Note: the rent a car I'm driving while on travel is a 6 cyl. - 2006 mustang,
auto; no power but handles nicely compared to my truck

 

[Steve B.]

69 Camaro

This 2005 message you wrote solved my error #429 problem. I'm going to
lunch with my rented mustang.
Thanks
Steve

Note: wasn't 429 an engine (big block, chevy, ford?)? Sorry, I'm surely,
showing my age before the 3 kids

->Does anyone have any idea what this message means?

It means that the library that carries the definition for FileObject is not
available in Access 2003. What library ....

Regsvr32.EXE "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"

....

HTH.
Gunny

 

['69 Camaro]

Hi, Steve.

I think the problem was fixed by . . . possibily
moving the DAO referencing above ADO

If you rely on this to fix it, it will bite you on the nose again and again
.. . . and again.

Now we have another problem on some machines with error #429 which I will
post seperately after doing some research

Make sure you post the code where the error occurs and include the
declarations of the variables, and whether or not Option Explicit is
included in the code module.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Hi, Steve.

This 2005 message you wrote solved my error #429 problem.

I'm glad to hear it.

I'm going to
lunch with my rented mustang.

Don't expect too much going up hills, even if they aren't steep. ;-)

Note: wasn't 429 an engine (big block, chevy, ford?)? Sorry, I'm surely,
showing my age before the 3 kids

You're right. Ford had a 429 cu. in. V-8 engine built specifically for
NASCAR racing, because of the 7.0 L size limit. Ford doesn't call them big
blocks like GM does. Ford names its engine categories by their series or
family.

The 429 cu. in. V-8 engine was also a 1963 Cadillac engine. However, Chevy
produced a big-block 427 V-8 engine from 1965 to 1996 that many of us may be
more familiar with.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.