Hello. From time to time I have to export datasets to local encoding. Normally, I work in Unicode mode, on version 29. Since version 26 or 27 2 strange bugs have occurred. First, when the `SAVE CODEPAGE` command is finished, the file simply doesn't appear in the same directory where the original dataset is. Seriously, no error is raised - everything looks like the command is successfully done but there's no file. Second, when saved (to a different directory of course), if the file name contains locale characters, the file name is crashed. Thankfully, data is correct.

Is this an obvious bug or do I miss something?

Hi @Soren V. Raben,

That definitely sounds ominous.   Are you able to login to the Support Portal and open a case? That would be very helpful in getting to the bottom of this problem.

One thing of the top of my head.  In the Overview (SAVE CODEPAGE command) is a "Limitations" section.  Are you trying to run SAVE CODEPAGE while SPSS Statistics is in Codepage mode?  If not, are there other errors/warnings associated with your execution of the SAVE CODEPAGE command?

------------------------------
David Dwyer
SPSS Technical Support
IBM Software

Original Message:
Sent: Mon December 04, 2023 08:06 AM
From: Soren V. Raben
Subject: SAVE CODEPAGE bugs in recent versions of SPSS

Hello. From time to time I have to export datasets to local encoding. Normally, I work in Unicode mode, on version 29. Since version 26 or 27 2 strange bugs have occurred. First, when the `SAVE CODEPAGE` command is finished, the file simply doesn't appear in the same directory where the original dataset is. Seriously, no error is raised - everything looks like the command is successfully done but there's no file. Second, when saved (to a different directory of course), if the file name contains locale characters, the file name is crashed. Thankfully, data is correct.

Is this an obvious bug or do I miss something?

Hi @David Dwyer,

thanks for answer. I'm not able to open a case in support portal...

I work only in Unicode mode so `SAVE CODEPAGE` is always ran not in codepage mode. As I said in my previous post, literally there are no warnings and errors indicated.

Original Message:
Sent: Tue December 05, 2023 05:11 PM
From: David Dwyer
Subject: SAVE CODEPAGE bugs in recent versions of SPSS

Hi @Soren V. Raben,

That definitely sounds ominous.   Are you able to login to the Support Portal and open a case? That would be very helpful in getting to the bottom of this problem.

One thing of the top of my head.  In the Overview (SAVE CODEPAGE command) is a "Limitations" section.  Are you trying to run SAVE CODEPAGE while SPSS Statistics is in Codepage mode?  If not, are there other errors/warnings associated with your execution of the SAVE CODEPAGE command?

------------------------------
David Dwyer
SPSS Technical Support
IBM Software

Original Message:
Sent: Mon December 04, 2023 08:06 AM
From: Soren V. Raben
Subject: SAVE CODEPAGE bugs in recent versions of SPSS

Hello. From time to time I have to export datasets to local encoding. Normally, I work in Unicode mode, on version 29. Since version 26 or 27 2 strange bugs have occurred. First, when the `SAVE CODEPAGE` command is finished, the file simply doesn't appear in the same directory where the original dataset is. Seriously, no error is raised - everything looks like the command is successfully done but there's no file. Second, when saved (to a different directory of course), if the file name contains locale characters, the file name is crashed. Thankfully, data is correct.

Is this an obvious bug or do I miss something?