Different access behaviour with different regional settings

[Guest]

Hi

I have an access database, which under polish default regional settings works correct. If I change the default settings to US english, then I get this message always when I try to open any form (see below)

"The expression On Open you entered as the event property setting produced the following error
A problem occured while <database name> was communicating with the OLE server or ActiveX Control.

" * The expression may not result in the name of macro, the name of user-defined function, or [Event Procedure]
* There may have been an error evaluating the function, event, or macro.

I also made some researches, this message is generated only if form has some events, but when I drop these event
or (even) comment them inside form's module, then everything is OK. Other procedures (non-events) inside form's module don't involve any problems

Well, I'll glad receiving some tip
Krzysztof Malinowski

 

[Nikos Yannacopoulos]

Krzysztof,

Just guessing here, but my experience as a non-US user says it's most likely
something to do with dates. If the code in your events deals with dates at
all, then That's where you should look first. Bear in mind that VB treats
dates as US format (month/day/year), so it's wise to use Format functions to
make sure what it reads come in the right format, and what it writes is
converted to the expected format before it is written.

HTH,
Nikos

Hi,

I have an access database, which under polish default regional settings

works correct. If I change the default settings to US english, then I get
this message always when I try to open any form (see below).

"The expression On Open you entered as the event property setting produced the following error:
A problem occured while <database name> was communicating with the OLE server or ActiveX Control."

" * The expression may not result in the name of macro, the name of

user-defined function, or [Event Procedure],

* There may have been an error evaluating the function, event, or macro. "

I also made some researches, this message is generated only if form has

some events, but when I drop these events

or (even) comment them inside form's module, then everything is OK. Other

procedures (non-events) inside form's module don't involve any problems.