Hi Ma Jack,

I reproduced this issue and PB 12.6 has the same behavior. I will transfer this for the developer to analyze

Regards,
Kai

Hello Ma Jack,

Like Miguel, I too tested your app that you provided as well as tried a number of other languages and have been able to duplicate the problem. It appears that using a filename with any characters beyond the extended ASCII code set will have the same problem. As you've stated, the issue isn't with the filename, however whatever filename you choose ends up being used for the sheet name as well and therein lies the problem.

Not sure how Appeon saves a Excel8! file behind the scenes but maybe there is something they can do given this is still a supported version of Excel that SaveAs() can use. Hopefully you'll have a response to your submission soon or maybe they'll respond to your post.

Since you stated your users need the file in this format, as a workaround, you could save the file in XLSX! format and then, via OLE, open the file and save it as an XLS file and then delete the XLSX file. While I haven't tried it, this should work programmatically as it works doing it manually, meaning that the format of an XLS file can work with multi-byte characters in the sheet name.

HTH...regards,

Mark

Dear Ma Jack,

I think I now finally understand the problem.

Me, I'm using office 365 and when I try to open the xls file, I get:

When I answer "Yes", I get:

So I've done some tests:

dw_1.saveas("作成 excel8.xls", excel8!,true) // BAD
dw_1.saveas("作成 Excel5.xls", Excel5!,true) // BAD
dw_1.saveas("作成 Excel.xls", Excel!,true) // it works, but you'll need to adjust office's Trust Center settings
dw_1.saveas("作成 XLSX.xlsx", XLSX!,true) // it works, but Office thinks it's a "file from the internet" and you'll need to adjust office's Trust Center settings

messagebox("","completed")

So you are right: this is a bug either in Powerbuilder or Office itself. (or both).

In addition, the PB help says this:

It doesn't mention Excel5!, but let's assume that one will also disappear in the future and doesn't solve your problem anyway giving a bad result.

I've done the same test with PB2022 R2, and get the same results.

So you have to get some kind of workaround for this.

I think you should report this as a bug on https://www.appeon.com/standardsupport/newbug

regards,

MiguelL

I've run your sample app and I'm getting the exact same filename as specified in your code:

Your sample app doesn't use ""GetFileOpenName! so hard to reproduce the problem. 

Hi,

I don't really understand. Your "garble" file name is hard coded ... so already "garbled" by yourself ?

What do you mean "If I use half width characters" ?

Can you create a very simple and small application to showcase the problem to us?

(also: really ? exporting as excel8! ?, why not use xlsx! ?)

regards