EA Japanese Edition Impact on Automation

[McMannus]

Hi all,

I'm currently having a customer from Japan using the Japanese edition of EA. I wonder, if the different language and in particular the different characters might brake something in our add-ins. I mainly think about plain SQL query interpretation going through Rep.SQLQuery() and Rep.Execute().

Did someone of you guys experience problems with that?

Many thanks!
Jan

[Eve]

Is there are problem being reported by your customer?

You'll need to be aware that if they are using a JET 3 based database, values will probably be saved in the Shift JIS codepage.

It's also possible that the database contains translated text, where you're looking for a particular value. From memory this happens for object scenario types.

[McMannus]

Yes, actually I already found a problem, which is directly related to EA itself. When trying to open an EAP file that has been created with the Japanese version (I'm using the English version), EA signals "An Error has occurred: Unrecognized database format" and refuses opening the project.

Any ideas from Sparx side what the cause of this problem could be and how to solve this issue?

Jan

[Glassboy]

Yes, actually I already found a problem, which is directly related to EA itself. When trying to open an EAP file that has been created with the Japanese version (I'm using the English version), EA signals "An Error has occurred: Unrecognized database format" and refuses opening the project.

Are you able to open the same file from an non-Japanese version of Access?

[McMannus]

Are you able to open the same file from an non-Japanese version of Access?

Yeah, I used already MDB Viewer Plus to look into the database to find something suspicious, but with no success. My english EA, however, does not allow me to open the file. It's funny that an XMI Export of the same project (exported from Japanese version) followed by an XMI Import in my English version works.

[Paolo F Cantoni]

Are you able to open the same file from an non-Japanese version of Access?

Yeah, I used already MDB Viewer Plus to look into the database to find something suspicious, but with no success. My english EA, however, does not allow me to open the file. It's funny that an XMI Export of the same project (exported from Japanese version) followed by an XMI Import in my English version works.

Was it created on the same machine?  If not, check that both machines have the "Use Jet 4" checkbox marked in the Settings [Ctrl+F9] I think.

It may not be directly related to the Japanese version.

HTH,
PAolo

[Eve]

Yes, actually I already found a problem, which is directly related to EA itself. When trying to open an EAP file that has been created with the Japanese version (I'm using the English version), EA signals "An Error has occurred: Unrecognized database format" and refuses opening the project.

Any ideas from Sparx side what the cause of this problem could be and how to solve this issue?

Jan

Go to the options and enable JET 4.

The good news is that if you have that issue, the text inside will saved as unicode instead of shift jis.