Question about issues between Access 2000 versions.

[Woody]

Having some issues with an application developed with Access 2000. When I
run the application on my dev. laptop, all the applications functionality
runs as expected, but when I put the application on a users machine, some of
the functionality does not work correctly, such as population of records on
sub forms, saving of records even bookmarking functionality seems to not
work in code. My dev. laptop has several access versions 97, 2000, XP and
2003. The user only has Access 2000 and 2003 on their machine. I've checked
versions of MDAC and the Jet 4.0, which Access 2000 uses and we both have
the same versions. Has anyone ever seen this sort of behavior before with
Access 2000 and what can be done to resolve the issue? Very frustrating as
you could imagine. I appreciate the help.


Woody.

 

[Guest]

Hi Woody,

I've checked versions of MDAC and the Jet 4.0, which Access 2000 uses
and we both have the same versions.

How did you do this check? Which versions of MDAC and JET does your customer
have? They should have MDAC 2.8 and JET SP-8. Did you use the MDAC Component
Checker Utility for checking MDAC?

Component Checker: Diagnose problems and reconfigure MDAC installations
http://support.microsoft.com/?id=307255


You might want to try re-registering both ADO and DAO on the computers that
are experiencing problems. Click on Start > Run. Then enter the commands:

Regsvr32 "C:\Program Files\Common Files\system\ado\Msado15.dll"
Regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"

Do you get any error messages? Is so, what are the error numbers and
description? If not receiving any error messages, does your code include On
Error Resume Next statements, effectively ignoring any error messages that
might be helpful in tracking down this problem?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________