Access runtime error 2455 mystery


I have about 5 mdb files that contain programs and data, links to data, etc. that I have been using for years with Windows 98, Access 2000.  After a few months of fine tuning, everything worked without problems when I switched to Windows XP, Access 2002.

Suddenly, when I open any of these modules and compile any new code, I receive the error "Runtime Error 2455", "You entered an expression that has an invalid reference to the property "xxxx".  (The "xxx" usually being the first referenced after opening the module - e.g.: .visible, or the use of a function as Time(), Date(), etc.)  Sometimes the "xxx" refers to a property that I'm not even using in the code.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You might have a missing reference, open any module in design view -> Tools -> References

Check if any is reported as missing.
jmcclaxAuthor Commented:
I t hought the same thing, but no references are reporting missing.

smells bad....

If Time() and Date() results in compile errors, it's normally something else, - but do look for missing references as suggested by heer2351.

XP: have you added hotfixes and latest SP? (don't believe them when they call everything "Security Updates", - there's bits and pieces in those too;-)

The migration from 2000 to 2002: did you just update? Did you compress/repair the 2000 version before update ?

Anyhow, - the path to problemsolving a case like yours is normally:

1. Create an empty Db in 2002
2. Import objects 1 at a time, compiling between each import untill you detect the culprit!


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

First of all you are up to date on the service packs, SP2 for Access XP.

Can you compile your database? Is it pointing you to a line of code that is indeed incorrect?

jmcclaxAuthor Commented:
Yes, up to date on service packs and security updates.  I even tried uninstalling and reinstalling all in the event that the service packs or security updates were the culprit (that, anyway, had been done about 1 month ago and all was well until yesterday).
Did not covert to 2002.
All code was correct and worked just fine until yesterday.  No code has been altered for 6 months.  
When you suggest to create a new db and import until I detect culprit, are you saying that all 5 modules have to have this done to find a solution?  No code changes have been made for 6 months to any of the modules.  It sounds more to me like some sort of Access/system problem, no?
It could also be an ActiveX problem, one of the usual suspects is the COMDLG32.OCX. Any changes made to that respect?
jmcclaxAuthor Commented:
Would updating Microsoft Windows media player have affected that?  If so, yes.

my bet would normally be on the database in your case, but we can focus on the system for a start if you like:

Uninstall & re-installing Office didn't always produce the desired result in Office 2K, and I'm not sure if the same  problems do not persist in XP, so if you like you can try an trick of mine and see if it works on XP too (it has handled some, but not all, Office related problems in the past for Word and Access).

The basic feature is that it really does an overwrite of everything, in stead of trying to guess if everything is ok:

Office 2K Critical repair procedure:

This procedure is based on the following refs:;en-us;230672&Product=ofw2k

1. Close all programs (ALL!)

2. Revert installation to original files for all:
      open a cmd-box
      cmd-line: <CD-ROM Drive-letter>:\setup.exe /fdum data1.msi

      - this will overwrite any file that isdifferent from the original media
        and reset registry keys to original

3. Re-apply all service-packs and updates

(please don't feel offended by the low-level approach, - I wrote it for some newbies once ;-)

Anyhow, - if this doesn't do the trick, I suggest you focus on the New Db/Import procedure, - it really isn't that tedious.

Sven I have to leave it into your capable hands.
jmcclaxAuthor Commented:
Ok, I'll try the repair option.
One question regarding the new db/import suggestion.  Since none of the code has been changed in 6 months, what exactly could that method point me to?

always hard to tell, but sometimes it identifies a module where some code - which used to be valid with e.g. the Jet 3.5, isn't valid with Jet 4.0, and sometimes it simply fixes itself ;-)

I know it sounds like  alchemy (sp?), but it actually is one of the most used tolls for handling "suddenly appeared problems" with Access.

The reason that I bring it up in an early phase of the error-search, is because your initial statements sounded as if you are a carefull person who don't just hack around in your modules, - if that had been the case, I'd have suspected you before the system ;-)

But, as it is, I'm hearing 6 bells from the clock, telling me that European Standard Time is 3 o'clock morning, so I will not be able to comment further for the next 10 hrs. or so.

Kind regards,
jmcclaxAuthor Commented:

I resolved the problem last night.  When I created a new database as you suggested, I noticed
that one of the references that was automatically checked in the new database (ActiveX library 2.1) was one that I had not been using before. When I left that reference checked, the problem went away.

I am baffled by this, as everything was running great until a few days ago, and no code changes have been made for months.  I don't understand what the ActiveX library's purpose in my projects would be for, anyway.  Is this some new requirement in XP?

Thank you very much for your help,
jmcclaxAuthor Commented:

Thank you for your help, too!


well, - as I said (or did I?): Access isn't always an exact science, so you learn that the procedures that may seem supersticious at first glance (like the New Db/Import) often helps in unexpected ways ;-)

Glad you got it solved!

Microsoft ActiveX Data Objects Library 2.1 is called in short ADO. ADO is the new default data access method for access 2000 and up, it replaces DAO.
This question has been abandoned and needs to be finalized.
 You can accept an answer, split the points, or get a refund (information at http:/help.jsp#hs5)
  If you need a moderator to help you, post a question at Community Support (http:/Community_Support/)


Cleanup Volunteer

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.