Problem "With Communicating with OLE Server" Using Non-Latin Alphabet Databases (1 Viewer)

[Edgar_]

Last question : How exactly you checked for the types of the object with strange names?

Great question, I simply used intelliSense, I recognize the properties of a section object. They look like this.

Now, here's another issue I see with Section objects. I switched from english to japanese. This is what shows in intelliSense:

(You tell me what it says @KitaYama )

But when you select it from there, it turns into the problem name:

As you can see, the name from intellisense does not match the name passed into the code. It's in japanese for intellisense, but the file seems to come with the embedded arabic name that has a conflict. That's another clue.

Now, here's another problem: If you try to get the type name of a conflicting section, it returns an error, this is what happens with the japanese version:

It's error 7 and I probably get a bunch of question marks because I don't have Japanese installed. I think that error is "out of memory".

Now, just to add details to this experiment, I created a new form using this japanese installation, while still using the original arabic file. The form was created with a japanese name, this is important. I wanted to see what the name of the section was and it returned "Detail" as the name when I tried to get it in the safe way:

If I try to add a module to the form, I simply can't. This is the message I get:

ChatGPT reads this as:

Failed to create Visual Basic module.

If the database is on a network drive, please check the network connection and try again.

But if I create another form and I give it a name in latin characters, I now can add a code module and I can finally reference the form by its class name to see what initializes with it, and it comes with "Detail" as the detail section name:

So there's definitely something off with section names and with the languages installed on our machines. It's either the Sections or the Sections plus the language settings that might be the cause of this problem, based on my experiments. So, if anyone wishes to reproduce these tests, please do so and confirm. Do confirm specially if just changing the names of the sections fixes these problems for you. And if not, try exporting and importing after that.

 

[KitaYama]

(You tell me what it says @KitaYama )

That's not Japanese. They are Garbled characters.

Thanks for the extended experiments and detailed explanation.
I appreciate your time and help. I'll go through those steps as soon as I'm back to my PC.

Thanks again.

 

[Edgar_]

Any update on this?

 

[KitaYama]

Any update on this?

I'm not sure you're asking me or others, but if it's me, I'm still on a business trip and won't be back until next Monday, so I haven't test it carefully yet.
I failed to solve my problem with databases created in Portuguese and Spanish, but it may be due to being using a remote desktop app to access my PC (AnyDesk).

The database I used to test is FormBotoes.accdb in this post.
I exported the form as text, but couldn't see anything wrong with object/section names.
The only possibility I could see was Name ="Rótulo178" . Changed it to Name ="Rotulo178" and Imported to the database. Still the same error.

Something's telling me the problem is much deeper than names.

 

[Edgar_]

Something's telling me the problem is much deeper than names.

I changed the application's language to Japanese and Arabic, and I was able to open the FormBotoes.accdb file without any issues the same way I was able to open it using the regular english version and the spanish version.

In Post 21, my main point was that I successfully used the arabic file by only changing the Section names, no controls were renamed. After renaming the Sections, I exported and re-imported the file and I was able to use the arabic file without encountering any errors.

The file FormBotoes.accdb and many of the samples I have posted have the detail section named as "Detalle". Try to change that name to "Detail" when you get the chance.

 

[KitaYama]

I changed the application's language to Japanese and Arabic, and I was able to open the FormBotoes.accdb file without any issues the same way I was able to open it using the regular english version and the spanish version.

In Post 21, my main point was that I successfully used the arabic file by only changing the Section names, no controls were renamed. After renaming the Sections, I exported and re-imported the file and I was able to use the arabic file without encountering any errors.

The file FormBotoes.accdb and many of the samples I have posted have the detail section named as "Detalle". Try to change that name to "Detail" when you get the chance.

Thanks for feedback.
I thought we were talking about non-Latin character names. I don't understand why naming Detail section to "Detalle" may harm. It's all English alphabet. If I open one of my databases and change the detail section to "Detalle", it has no problem.

Anyway to be sure I followed your direction. Changed it to "Detail" in the exported text file, and imported again.
Still the same error.

Attached is what I imported and still results in error.

 

[KitaYama]

I changed the application's language to Japanese

I don't think changing language has any effect. How about changing your PC's locale to Japanese and see what happens. (Control panel - Clock and region - Region - Administrative tab - Change system locale.... button

 

[Edgar_]

I don't understand why naming Detail section to "Detalle" may harm

Well, the internals of Access are in english and Access is an ancient application that has not received a lot of love by its developers, so I believe it is my obligation to test that kind of thing after the testing done and shown in post 21. I'll check what happens if I change locale.