Access 2000 to 2003 - Feature no longer functioning properly

[servoss]

I have built a rather extensive database using Access 2000. When I install it on an Access 2003-enabled machine, the first time it is opened, the user is presented with the following errorbox:

"An error occurred and this feature is no longer functioning properly. Would you like to repair this feature now?"

At this point, clicking "Yes" results in an update the installation of Access 2003. Then the database must be opened manually again. Then, the following is displayed:

"Module not found."

Closing the database at this point and then opening it again results in a normally functioning database.

I have several questions:

1) What is the feature that is no longer functioning properly?
2) What is updated when the installation exec runs?
3) What module is not found? I assume this is one of the VBA modules that I've created, but I've check all 62 of them and they all seem to be there available.
4) My first guess was a reference problem, but I've checked the references used and all are available, as far as I can tell. These are the ones that I have referenced: VBE6.DLL, MSACC9.OLB, DAO360.DLL, STDOLE2.TLB, MSCAL.OCX, MSADO25.TLB, MSO9.DLL.
5) After getting the first error - the one about nonfunctioning feature, I clicked "no" to the repair now question. This does nothing except the database remains open. At this point, I opened the code and tried to compile, but I get the "module not found error". I likewise tried to set a breakpoint in one of the first modules and I get the same result.
6) I even tried to copy the forms, queries, tables, and reports into a blank database with no references and no other extraneous code and received the same result.

This site has been extremely helpful in the past and I am really relying on you guys again for the same stupendous help now.

Forever in your debt,

Tom

 

[servoss]

Anyone have any thoughts whatsoever?

 

[servoss]

Anyone have any thoughts at all?

 

[servoss]

Just in case anyone cares...

I figured out the problem, I think. When I uninstalled the previous version of my database, I was also uninstalling a couple of the reference libraries. When i installed the new version, I did not install the same libraries. One of them - I'm not sure which - was required for normal Access functions and it wasn't there.

I simply installed the older version again and then uninstalled without removing the reference libraries and then installed the new version and everything worked just fine.

I have had a lot of good information and advice from this forum in the past, but I guess this one stumped everyone enough to not have a single reply. Perhaps, I'm getting to be more skilled at this than others are? Just a thought.

t

 

[Rickster57]

I just read your post and have just experienced similar issues.Here is some other info that you may want to watch out for. I downloaded an updated mdb on a computer that had the database previously installed on it. I noticed of all things that the Date() and format function would produce and error on that computer but not on mine. I looked at the references and the problem was caused by Visual Basic Regular Expressions 5.3. My computer had 5.5 and no issues. I changed the 5.3 to 5.5 had the Date() function now works properly.

 

[The_Doc_Man]

Invariably, when you upgrade versions of Access, one or more libraries will change versions. Unfortunately, even if you don't remove the old libraries, you sometimes still get a reference problem because the old libraries aren't compatible with the new ones. Just as an item to add to your checklists: When upgrading any Access app from an older version to a newer one, expect to have to clear obsolete references and replace them with newer ones. It is sort of like a "cost of doing business" with Access.