By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,938 Members | 1,578 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,938 IT Pros & Developers. It's quick & easy.

VBA editor changes keyboard layout.

P: n/a
Hello all,

posting my question in this newsgroup is about the last alternative I
can think of to resolve my problem.

The standard keyboard layout in the office is AZERTY.
Still, my access xp mdb acts as if the keyboard is QWERTY.

I deleted the QWERTY layout in regional settings in win xp pro.
However, whenever I open the VBA code, it recreates QWERTY in regional
settings and forces the appl to act as if QWERTY is the keyboard
layout.

How come? Any suggestion is welcome.
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
There is some code there that is calling LoadKeyboardLayout or calling
intl.cpl with an unattend file to add the layout.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
Windows International Division

This posting is provided "AS IS" with
no warranties, and confers no rights.
"Rudi" <ru****************@jungheinrich.be> wrote in message
news:81**************************@posting.google.c om...
Hello all,

posting my question in this newsgroup is about the last alternative I
can think of to resolve my problem.

The standard keyboard layout in the office is AZERTY.
Still, my access xp mdb acts as if the keyboard is QWERTY.

I deleted the QWERTY layout in regional settings in win xp pro.
However, whenever I open the VBA code, it recreates QWERTY in regional
settings and forces the appl to act as if QWERTY is the keyboard
layout.

How come? Any suggestion is welcome.

Nov 13 '05 #2

P: n/a
Dear Michael,

I saw your name many times in the disc. groups. So great was my
surprise that I had the honour to receive a response from somebody who
has more interesting problems to cope with.

Whilst awaiting response, I tried to get rid of the problem by
importing everything into a brandnew mdb. It seemed to work but not
for long.

So tomorrow in the office, I will be looking into your advise more
deeply.

Many thanks again.
Sincerely, Rudi.
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.