P
Peter
Hi all,
I have developed an Access 2000 FE-BE solution (BEs are replicated) for
international use including Russian and Asian users. The database apparently
works OK for users in Europe but Russian and Asian users (e.g. for Russia:
localized Windows, english international version of Office, in China:
localized both Windows and Office) have problems. The problems are
manifested on start up form (after the form opens and displays the data
correctly). The problem is an error: "On click event caused error ... cannot
communicate with ActiveX or OLE server ..." and appears after users click on
any of the form controls. There is a log file where it is shown that
"start-up" VBA code does execute correctly and the form displays the source
table contents OK. There are no non-native Access controls on the start
(just command buttons, combos, lists, text boxes and a sub-form) and some of
the API calls also seem to work fine. All DB entries are in English.
I'd deeply appreciate any hints or help of any sort.
Thanks,
I have developed an Access 2000 FE-BE solution (BEs are replicated) for
international use including Russian and Asian users. The database apparently
works OK for users in Europe but Russian and Asian users (e.g. for Russia:
localized Windows, english international version of Office, in China:
localized both Windows and Office) have problems. The problems are
manifested on start up form (after the form opens and displays the data
correctly). The problem is an error: "On click event caused error ... cannot
communicate with ActiveX or OLE server ..." and appears after users click on
any of the form controls. There is a log file where it is shown that
"start-up" VBA code does execute correctly and the form displays the source
table contents OK. There are no non-native Access controls on the start
(just command buttons, combos, lists, text boxes and a sub-form) and some of
the API calls also seem to work fine. All DB entries are in English.
I'd deeply appreciate any hints or help of any sort.
Thanks,