Does the code compile on the 2007 machine?
I would consider doing a de-compile,a nd then re-compiling the code. They
are different versions.
So, it should run, but try a de-compile. Then compact and repair, and then
compile the code, and THEN try running it.
Decompile is explained here:
http://www.mvps.org/access/bugs/bugs0008.htm
You could also de-compile it on the 2002 box BEFORE you copy it to the
target machine.
I always install the folwling registry edit that gives you a context (right
click) decompile option.
http://www.mvps.org/access/bugs/bugs0008.htm
The code should run without modifications, but since the application was
built and "compiled" on a different binary version, then it makes sense to
de-compile..and then force re-compile on the target machine. Note also the
above context right click is useful anytime during development you
experience a ms-access execution error (a Dr. Watson error....the so called
"ms-access has encounter an error). if you experience a error during the
development cycle, then I STRONGLY suggest the first thing you do (after
killing ms-access in the task manager) is to do a de-compile.
If you plan to a whole bunch of different versions of ms-access to run the
same application in a multi-user environment, you CAN do this. To have the
appcation use the same data you split the database. You then simply deploy
the correct front end to each machine that running the respective version of
ms-access. This allows you to run 3, 4 or even 5 different versions of
ms-access, but still have all users work on the same data.
I explain the concept of splitting here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm