I have a Accessclient/SQLserver setup running at a company where all users work on a RDP-server. Some users have their Windowslanguage set to English, some have Dutch (as have I).
Every users gets their own client in their windowsprofile through a batchfile, ensuring everybody always has a fresh uptodate client
Last week I released an update (while working in dutch windows). Several users reported problems with using a new form when using certain buttons:
"Gebeurtenisprocedure" is the Dutch translation for "eventprocedure"
When I checked with a user that reported this problem, I noticed that when I open the form in editmode and check the properties of the failing controls (buttons), that while the users has their Windows set to english, SOME of the buttons still have "gebeurtenisprocedure" set as the eventhandler instead of "eventprocedure". Other buttons - that do work for the user - have "eventprocedure" set as the eventhandler.
So, on the SAME form, some buttons keep to the dutch eventhandler, which doesn't work obviously, some buttons are set to the english eventhandler....
Of course, Access cannot handle this. It seems that Office should translate/handle the eventhandler between different languages and that for some reason this does not happen for some buttons on some forms
Strangly, when I created a new AD testaccount, set its language to english, the exact same client DOES work for that testaccount, so it seems all eventhandlers are "translated" correctly. So no errors...
When I set the user that reported to problem to dutch language, the client worked without problems (however, the user does not speak dutch, so this is not a solution)
I tried compiling/decompiling/compressing the client, no difference. I also tried importing all objects into a new database, but this also did not fix the problem.
Anyone that has some advice what to do?
edit: I just check some more users, some users have English set as Windowslanguage and have the problem, some users have English set but DON't have the problem. Users that have the problem and set Windows to dutch dont have the problem either... When they go back to English the problem reoccurs.
Every users gets their own client in their windowsprofile through a batchfile, ensuring everybody always has a fresh uptodate client
Last week I released an update (while working in dutch windows). Several users reported problems with using a new form when using certain buttons:
DB xxxx cannot find the object 'Gebeurtenisprocedure'. If 'Gebeurtenisprocedure' is a new macro of macrogroup, make sure you have saved it and that you have typed its name correctly
"Gebeurtenisprocedure" is the Dutch translation for "eventprocedure"
When I checked with a user that reported this problem, I noticed that when I open the form in editmode and check the properties of the failing controls (buttons), that while the users has their Windows set to english, SOME of the buttons still have "gebeurtenisprocedure" set as the eventhandler instead of "eventprocedure". Other buttons - that do work for the user - have "eventprocedure" set as the eventhandler.
So, on the SAME form, some buttons keep to the dutch eventhandler, which doesn't work obviously, some buttons are set to the english eventhandler....
Of course, Access cannot handle this. It seems that Office should translate/handle the eventhandler between different languages and that for some reason this does not happen for some buttons on some forms
Strangly, when I created a new AD testaccount, set its language to english, the exact same client DOES work for that testaccount, so it seems all eventhandlers are "translated" correctly. So no errors...
When I set the user that reported to problem to dutch language, the client worked without problems (however, the user does not speak dutch, so this is not a solution)
I tried compiling/decompiling/compressing the client, no difference. I also tried importing all objects into a new database, but this also did not fix the problem.
Anyone that has some advice what to do?
edit: I just check some more users, some users have English set as Windowslanguage and have the problem, some users have English set but DON't have the problem. Users that have the problem and set Windows to dutch dont have the problem either... When they go back to English the problem reoccurs.
Last edited: