Eduardo,
I can't exactly tell you how to cure your problem, but this was my
situation.
I had an English Access 2002 (XP) database application that I had been
packaging with Access runtime scripts from SageKey Software in conjunction
with Wise Installation System Software. I had a request from a casino
client in Nicaragua to translate the application into Spanish.
All the field labels on forms an reports were translated, but as the
application was still being run with English Access 2002 runtime, error
messages still appeared in English. The app was then packaged with Spanish
Access 2002 runtime. At that point, everything appears in Spanish to
include error messages, and the fact that all the queries, macros, code is
in English appears to make no difference.
The Access 2002 Spanish runtime application has been installed on machines
running both English and Spanish versions of Windows. In some instances
English Access is also present on the target machines.
However, I believe the difference, or reason why the application installs
and runs on both English and Spanish versions of Windows and cares not if a
differing version of Retail Access, either Spanish or English, happens to be
present is the fact that the SageKey scripts have code in the installation
process to accommodate/recognize different language versions of Access, and
eliminate conflicts among differing versions of Access.
I understand that may not be a very clear answer or explanation. Whether
you have interest in SageKey's product or not, I am certain that the folks
at SageKey could give you a definitive answer concerning how you can cure
your difficulty, if that is possible without packaging a runtime app. If
you decide to call them to inquire, I would ask for Barry Matfield.
See
www.sagekey.com