Z
zgilboa
BUG DESCRIPTION:
One of the weirdest access 2003 bugs I had ever encountered, with the source
of the problem being exceptionally hard to isolate. In essence, the bug
takes place whenever the following two conditions are true:
1. In the control panel, under "Regional and Language Options" and then
under the "Advanced" tab, the "Language for non-unicode programs" is set to
an "exotic" language (Chinese, Japanese, Hebrew, Arabic, etc...)
2. Still under "Regional and Language Options" but under the "Standards and
Formats" tab, the language that is selected is *different* than the above.
SO... if the default language for non-unicode programs is for example
Japanese but the selected language for standards and formats is Arabic, the
ADP project won't display any database error messages whatsoever. Try, for
example, to save a record with a duplicate primary key. Nothing will happen,
but you won't know why.
HOW TO SOLVE:
Given the above, the language selected for "Standards and Formats" MUST
ALWAYS be identical to the one selected for non-unicode programs. Japanese
and Japanese, Chinese and Chinese, Hebrew and Hebrew, Arabic and Arabic, etc,
which in turn makes the operating system's option to define them separately
rather useless...
AFTER THOUGHT:
The least Microsoft could do to solve this bug is have MSACCESS provide the
user with an error message stating that the control panel settings conflict
with the design desired by MSACCESS.
One of the weirdest access 2003 bugs I had ever encountered, with the source
of the problem being exceptionally hard to isolate. In essence, the bug
takes place whenever the following two conditions are true:
1. In the control panel, under "Regional and Language Options" and then
under the "Advanced" tab, the "Language for non-unicode programs" is set to
an "exotic" language (Chinese, Japanese, Hebrew, Arabic, etc...)
2. Still under "Regional and Language Options" but under the "Standards and
Formats" tab, the language that is selected is *different* than the above.
SO... if the default language for non-unicode programs is for example
Japanese but the selected language for standards and formats is Arabic, the
ADP project won't display any database error messages whatsoever. Try, for
example, to save a record with a duplicate primary key. Nothing will happen,
but you won't know why.
HOW TO SOLVE:
Given the above, the language selected for "Standards and Formats" MUST
ALWAYS be identical to the one selected for non-unicode programs. Japanese
and Japanese, Chinese and Chinese, Hebrew and Hebrew, Arabic and Arabic, etc,
which in turn makes the operating system's option to define them separately
rather useless...
AFTER THOUGHT:
The least Microsoft could do to solve this bug is have MSACCESS provide the
user with an error message stating that the control panel settings conflict
with the design desired by MSACCESS.