Version compatibility

[rmiller1985]

Does anyone know if there are there any compatibility issues between Access
2000 on a PC running Windows XP and Access 2000 on a PC running Windows 2000?

A client sent me an .mdb file, which I opened and was able to work on. I
modified and added VBA code, then copied the new .mdb file onto a CD and went
to the client's site. All of the new code worked fine at home, but at the
client's site I received several runtime errors that threw the application
into the debugger. Sometimes the debugger would open on code that used a
variable that I hadn't declared; but sometimes it would open on code that I
hadn't modified (and, as far as I can tell, had no problems). After fixing
the code in question, the application worked fine; but then I did some more
development at home and e-mailed the .mdb file back, and once again the user
experienced runtime errors in when opening forms, and in at least one case it
was a form where I'd modified the layout of a control slightly but hadn't
modified any code.

Any ideas?

Thanks,
Rich

 

[Douglas J. Steele]

It's probably not directly due to WIndowsXP vs. WIndows2000 so much as the
fact that Access is extremely sensitive to version differences in referenced
files. (All Access databases contain references, which are a way of
referring to another application's or project's type library. In general,
you want to ensure that the files referenced in an Access application exist
in exactly the same location on the client workstations as they did on the
development workstation, and that each referenced file is the same version
on all workstations.)

On the machine(s) where it's not working, open any code module. Select Tools
| References from the menu bar. Examine all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

 

[rmiller1985]

Thanks, Doug, I'll give it a try!

Rich