VBA Issues in 2010

[jkfeagle]

Anyone come across this issue? We have a database we have been running in Access 2003 and it was working fine. We converted over to 2010 and now none of the modules will run - in a nutshell it says they're not there. When you go into the modules section you can clearly see them all listed but when trying to open in design mode you get the error that the module name is misspelled or refers to a module that doesn't exist. Now I would have thought that this would be the case on all the db's we have been using but it's not, just this one. All the others seem to be working fine. Anyone have any ideas?

 

[GinaWhipp]

A few questions here...

1. Is the database in a Trusted Location?
http://www.access-diva.com/d4.html

2. What References do you have checked?
http://www.access-diva.com/d5.html (Scroll to bottom)

 

[123billp]

This sounds very similar to a problem that I am having.
To avoid writing code, I decided to use a macro instead. Basically, I'm using a macro to open a form (that works fine), and set a value (this does not work).
Even though the control name shows up as type "Controls!", and I use it from the list, I get an error message when I try to run it. It says the control does not exist, or that it has been misspelled.
I also converted the macro the vba to see the code, and it looked fine, but gave me the same error message.

 

[GinaWhipp]

Hmmm, well, is the database in a Trusted Location? And what References do you have checked?

 

[123billp]

I noticed your original reply after I posted the question (sorry!)
I'm not sure about trusted location (I don't do our installs), although I can tell you that it is on our LAN drive and that I have read and write access to it, and have had for some time. Where can I look to answer this question?
I did check the references and have the following:
Visual Basic for Applications
Microsoft Access 14.0 Object Library
OLE Automation
Microsoft Office 14.0 Access Database Engine Object
Microsoft ActiveX Data Objects 2.1 Library

 

[boblarson]

1. Which file format are you using (mdb or accdb)?
2. If using accdb, did you convert from an mdb?
3. If you converted, how did you convert? Did you IMPORT everything into a new, blank accdb file or did you use the Save Database As?
4. If you used the Save Database As, I've found that the only really good method is to import it all from the old mdb file to a new, blank accdb file.

 

[GinaWhipp]

Bob's suggestion, number 4, is spot on... since judgring by your References it looks like you did a Save As...