Link to home
Start Free TrialLog in
Avatar of Biopsych
Biopsych

asked on

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
Avatar of Seth Simmons
Seth Simmons
Flag of United States of America image

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
ASKER CERTIFIED SOLUTION
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Biopsych
Biopsych

ASKER

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
Please clarify how I would refresh Access 2000 on Windows 7. Thanks
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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
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.
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
Biopsych --
MS' official answer to your question may be found here
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=7352
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.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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?
<<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.
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.
Are you all set then?  Just want to be sure.

Jim.