Is Access 2000 compatible with Windows 7?

We have a couple of users who have been using our Access 2000 database in Windows 7 for several years without any issues.

One of these users recently starting using the same Access 2000 database on a new PC with Windows 7 and now gets
the attached error message when she attempts to run some of the VBA based functions.

It appears that Access 2000 is compatible with Windows 7 on some PCs and not others.

Please advise. Thanks
emessageTanya.png
BiopsychAsked:
Who is Participating?

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

x
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.

Seth SimmonsSr. Systems AdministratorCommented:
Is Access 2000 compatible with Windows 7?

no; office 2003 is the earliest version supported on windows 7
it might install but won't function properly
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
No, that answer is incorrect.   Access 2000 runs fine under windows 7.

Your problem is references.   On one of the machines that it doesn't wort on, open the DB while holding the shift key down.

When the database window comes up, key alt/F11.

That brings up the VBA editor window.   Now go to tools, then references.

In the list, one will be listed as MISSING or BROKEN.  If so, you'll need to figure out why.   If not, then they may just need a refresh to work.

jim.
0

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
BiopsychAuthor Commented:
Jim Dettman

Thanks. Will give this a try and let you know.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

BiopsychAuthor Commented:
Reference list:
Checked =  
Visual Basic For Applications
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft Visual Basic for Applications Extensibility 5

No indication that anything is broken or missing.   Please advise. Thanks
0
BiopsychAuthor Commented:
Please clarify how I would refresh Access 2000 on Windows 7. Thanks
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
This:
"Microsoft Access 12.0 Object Library"

 is probably causing the problem either directly or indirectly.   12.0 is the lib for Access 2007, so these users must have it installed besides 2000 or no 2000 at all.  With 2007 and up, If you open an old DB, references are auto upgraded to the release your using, which can cause problems.

 But what's the exact situation:

1. They are using a DB created with A2000 and are trying to open it with A2000

2. They are using a DB created with A2000 and now are using 2007 to open it

  If #2, then you may need some code changes to get it to work properly. Microsoft started tightening up on syntax and what not starting with 2007.

 and on this station, is A2000 and 2007 both installed?

<<No indication that anything is broken or missing.   Please advise. Thanks >>

Do the following just to make sure we know where we are:


 Check one unchecked reference (doesn't matter which).

 Compile the app...make sure it's error free.  If it's not, you'll need to fix it.

 Save and close the app.

 Re-open and uncheck the reference you just checked (it will be the last).

 Compile again and make sure it's error free.

 Save and close

 Now do you have a problem?

Jim.
0
BiopsychAuthor Commented:
Before I try your suggestions want to make it even clearer.

I looked at the references on a different computer from the one I mentioned in the original question that also has Windows 7/Access 2000 and appears to have the same issues as
the computer I mentioned in the original question. Did this as could test your suggestion immediately. The test computer
has  Access 2000, 2003 and 2007.

However,  the computer in the original question ( the one of highest priority) has  Access 2000 and
Office 2010 installed.  Based on your response I will now wait until I can check the references on that computer and get back to you for your advise.  Make sense?  Thanks
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
When you have multiple versions, it's best to launch DB's with a short cut rather then relying on the last run version to try and execute it.

What I would do at this point is:

1. using A2000, compile the DB and make sure there are no errors.

2. Using that copy, try running it under 2007 and 2010.  The references will be updated.  Compile and check again with each for errors.

  Again, Microsoft internally in Access tightened up on a lot of things, mostly with property pages and some of the things that worked in the past don't with A2007/2010.  However it's a result of different Access versions, not windows 7.

 and note that once a reference has be auto updated, if you take that DB back to prior version, it's not going to run.

Jim.
0
BiopsychAuthor Commented:
Thanks for your quick responses.
One caveat -  I already know that some essential functions in the Access 2000 db will not run in Access 2007.
I had also been told previously to not run Access 2000 DBs in Access 2007 as could corrupt DB. Is that not true?
Thanks again
0
jcimarronCommented:
Biopsych --
MS' official answer to your question may be found here
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=7352
0
BiopsychAuthor Commented:
Jim Dettman,

Thanks again for your input.  It helped me figure out the simplest way to solve this issue and therefore will award you the
500 points.

Just found out that on the Windows 7 computer where Access 2000 works it is the only version of Access installed.
Therefore seems simplest to uninstall Access 2010 on the Windows 7 box in question.
Would uninstalling Access 2010 cause  Access 2000 to revert back to its native library?  If not, may need to reinstall
Access 2000 as well.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Would uninstalling Access 2010 cause  Access 2000 to revert back to its native library? >>

 You need a fresh copy of the DB from an A2000 machine.

 Also, you may find you need to re-install/repair A2000 depending on how A2010 was installed and which edition it was (32 or 64 bit).

 You can run multiple versions pretty well:

a.  if they are installed from oldest to newest
b. They are installed to separate directories.

 If that was not done, then a re-install of A2000 is a good idea.

Jim.
0
BiopsychAuthor Commented:
You stated -
 "You need a fresh copy of the DB from an A2000 machine."

Please define "fresh copy" -   the Access 2000 DB is on a shared drive on a Windows 2003 Server.
Would a backup from before the user opened the Access 2000 DB on the machine with  A2000 and A2010  =  fresh copy?
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Please define "fresh copy" -   the Access 2000 DB is on a shared drive on a Windows 2003 Server.
Would a backup from before the user opened the Access 2000 DB on the machine with  A2000 and A2010  =  fresh copy? >>

  Ah, so that's part of the problem too...when a 2010 user opened that DB, the references were updated.  

  Yes, a copy prior to that would be fine, but also you can also simply fix the references.

  On a machine with A2000, open the DB with the shift key held down.   Alt/F11 to get the VBA window, then tool/references.   The 12.0 lib will be listed as missing and it should be un-checked.

If it's not, uncheck it.  Then scroll down the list and find the A2000 version (9.0 or C:\Program Files\Microsoft Office\Office\msacc9.olb)

Check that and close.  Compile and make sure no errors.

You really should have a separate copy of the front end for each user and one "backend" holding the data shared between all.

Jim.
0
BiopsychAuthor Commented:
Thanks again.  

You stated -
 "You need a fresh copy of the DB from an A2000 machine."

Please define "fresh copy" -   the Access 2000 DB is on a shared drive on a Windows 2003 Server.
Would a backup from before the user opened the Access 2000 DB on the machine with  A2000 and A2010  =  fresh copy?

My test was on a copy.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Are you all set then?  Just want to be sure.

Jim.
0
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.