Help w. 2007 References needed

[LakotaMan]

I thought I’d found a thread for this in the forum, but I can’t find it now. Please help by redirecting me or answering my plea:

I have a 2003 app that’s been running fine until users began to upgrade to version 2007. Now several are getting messages that I think have to do with missing references.

Specifically, the user clicks a button from the switchboard to open a form and gets the following message:

“Error loading DLL”

and execution stops, highlighting the following code line in the requested form’s open procedure:

Set MyDB as CurrentDB

I think this has to do with a missing ref, but don’t know which one. Below is the list of refs that are checked in the Tools/References dialog:

Visual Basic for applications
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft DAO 3.51 Object Library
Microsoft ActiveX Data Objects 2.5 Library

I don’t recall EVER using DAO, but since it’s there, I’m afraid to turn it off.

As always, any help you can give me will be GREATLY appreciated.
TWD

 

[RoyVidar]

[tt]Set MyDB as CurrentDB[/tt]

should give a compile error, while

[tt]Set MyDB = CurrentDB[/tt]

should work with correct references.

Scrap DAO 3.51, it's for 97 or older, I think (Jet 3.5). When saved as 2000-2003, I think you should use DAO 3.6.

Roy-Vidar

 

[LakotaMan]

Roy,

My mistake on transferring my info --I DO have the =
Sorry 'bout that.

Should I add the DAO 3.6 after I scrap DAO 3.51?

Would a missing MS Office 12.0 Object Library ref be a problem? I seem to have that set on my copy of Access and it isn't listed on my client's copy.

Thanks for your quick response

TWD

 

[PHV]

Any MISSI?G reference is a problem.
I'd use late binding ..

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[RoyVidar]

If you use DAO, then yes add the DAO 3.6 reference. The MS Office Object library - dunno - I don't use it - I mostly use late binding for anything "not native".

If you use it early bound, then you would need to add it.

Check it by removing it, then try a Debug | Compile. This should highlight any usage of objects, methods or properties of exposed by that library.

Roy-Vidar

 

[LakotaMan]

Thanks to BOTH of you, I will:

Remove old DAO ref,
Turn on Office 12 Ref,
Debug/Compile

since I'm not getting any "Missing" notes in the list.

And, I'll look into late binding, as I'm not familiar with it.

Hopefully, this will help,

Thanks again.
TWD

 

[LakotaMan]

Just a note to let all who helped me know that I resolved my references problem.

Unfortunately, it was caused by pure stupidity on my part. I have a third party dll I use for an email function, usually the file is in the windows folder. Some of my client's employees got new machines and the dll wasn't in the windows folder, of course. Once I copied it over this referencing error was resolved.

Sorry for all the problems I caused, and thanks as always to Roy Vidar and PHV.

LM