Alex & Access

News, links, downloads, tips and tricks on Microsoft Access and related

About Me Search
My Photo
Name:Alex Dybenko

Location:Moscow, Russia
Google
 
Web AccessBlog.net

Wednesday, April 06, 2005

Localized Access version problem

I always tell my colleagues – use only English Access (and other Microsoft tools) version to develop applications, but sometimes this occur...
I asked my colleague to make a small prototype – one form with Janus GridEx. It works great at me, and I have sent to my client together with instructions how to register new ActiveX control. He reported that nothing works and he got a lot of error messages like “UnboundReadData generate an error when communicating with the OLE-server or the Active X-control”. First I thought that control is not registered, or some other components missing – still does not work. Ok, I have installed a Virtual PC with same environment like client has (Windows XP and Access 2000) – and got same error! Hmm, how come? Code does not work even for a simple form inserted on a main form as a subform. Ok, I quickly recreated both forms in Access 2000 – everything start working. But why it did not? I asked my colleague about Access version he used and he told that it was Access 2003 Russian! This could be a problem! I started my Virtual PC again, Control panel-Regional and Language options-Advanced and set “Select a language to match the language version of the non-Unicode program you want to use” to Russian. After restart – it works!
I saved a form to text using hidden SaveAsText method, looked at the text and yes - detail section was named there as “область данных”! This was a reason.
So rule is simple – use only English character in object names and code – variables, functions, etc. Then it will work on any language settings.

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home