version 22

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

version 22

Arthur Kramer

I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.

 

Has anyone else experienced this?

 

 

 

Arthur Kramer, PhD

Director of Institutional Research

New Jersey City University

 

Reply | Threaded
Open this post in threaded view
|

Re: version 22

Jignesh Sutar
It's likely to do with the file being saved in Unicode format.


You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.

HTH,
Jignesh



On 9 December 2013 15:42, Arthur Kramer <[hidden email]> wrote:

I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.

 

Has anyone else experienced this?

 

 

 

Arthur Kramer, PhD

Director of Institutional Research

New Jersey City University

 


Reply | Threaded
Open this post in threaded view
|

Re: version 22

Rick Oliver-3
In reply to this post by Arthur Kramer
By default, the application is running in Unicode mode. You are reading code page data files and string widths are tripled. You can switch to code page mode and strings won't be tripled.

Rick Oliver
Senior Information Developer
IBM Business Analytics (SPSS)
E-mail: [hidden email]




From:        Arthur Kramer <[hidden email]>
To:        [hidden email],
Date:        12/09/2013 09:42 AM
Subject:        version 22
Sent by:        "SPSSX(r) Discussion" <[hidden email]>




I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.
 
Has anyone else experienced this?
 
 
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
Reply | Threaded
Open this post in threaded view
|

Re: version 22

Arthur Kramer
In reply to this post by Jignesh Sutar

Thanks, Jignesh, but the directions at the link says to look for ‘Character Encoding for Data and Syntax’. That option is not listed on the Options>General drop-down.  Would the ‘Apply locale’s digit grouping format to numeric values’ be the same thing?

 

Thanks for your help.

 

Arthur Kramer, PhD

Director of Institutional Research

New Jersey City University

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of J Sutar
Sent: Monday, December 09, 2013 10:59 AM
To: Arthur Kramer
Cc: [hidden email]
Subject: Re: version 22

 

It's likely to do with the file being saved in Unicode format.

 

 

You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.

 

HTH,

Jignesh

 

 

On 9 December 2013 15:42, Arthur Kramer <[hidden email]> wrote:

I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.

 

Has anyone else experienced this?

 

 

 

Arthur Kramer, PhD

Director of Institutional Research

New Jersey City University

 

 

Reply | Threaded
Open this post in threaded view
|

Re: version 22

Bruce Weaver
Administrator
What happens if you run this after launching SPSS (i.e., with an empty dataset)?

SET DIGITGROUPING=No Small=0.0001 Unicode=No OLang=English.



Arthur Kramer wrote
Thanks, Jignesh, but the directions at the link says to look for 'Character Encoding for Data and Syntax'. That option is not listed on the Options>General drop-down.  Would the 'Apply locale's digit grouping format to numeric values' be the same thing?

Thanks for your help.

Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University

From: [hidden email] [mailto:[hidden email]] On Behalf Of J Sutar
Sent: Monday, December 09, 2013 10:59 AM
To: Arthur Kramer
Cc: [hidden email]
Subject: Re: version 22

It's likely to do with the file being saved in Unicode format.

http://www-01.ibm.com/support/docview.wss?uid=swg21502287

You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.

HTH,
Jignesh


On 9 December 2013 15:42, Arthur Kramer <[hidden email]<mailto:[hidden email]>> wrote:
I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.

Has anyone else experienced this?



Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
--
Bruce Weaver
bweaver@lakeheadu.ca
http://sites.google.com/a/lakeheadu.ca/bweaver/

"When all else fails, RTFM."

PLEASE NOTE THE FOLLOWING: 
1. My Hotmail account is not monitored regularly. To send me an e-mail, please use the address shown above.
2. The SPSSX Discussion forum on Nabble is no longer linked to the SPSSX-L listserv administered by UGA (https://listserv.uga.edu/).
Reply | Threaded
Open this post in threaded view
|

Re: version 22

Jon K Peck
In reply to this post by Arthur Kramer
The Options dialog was redesigned for V22, and this setting is now found on the Language tab.

When you first launched V22, you were presented with a dialog that pointed out that Unicode was the default and pointed to a more detailed discussion.  Please look at the help on that topic before deciding whether to stick with code page encodings or move to Unicode.  See the Character Encoding and Locale help topic under Options > Language Options.



Jon Peck (no "h") aka Kim
Senior Software Engineer, IBM
[hidden email]
phone: 720-342-5621




From:        Arthur Kramer <[hidden email]>
To:        [hidden email],
Date:        12/09/2013 09:18 AM
Subject:        Re: [SPSSX-L] version 22
Sent by:        "SPSSX(r) Discussion" <[hidden email]>




Thanks, Jignesh, but the directions at the link says to look for ‘Character Encoding for Data and Syntax’. That option is not listed on the Options>General drop-down.  Would the ‘Apply locale’s digit grouping format to numeric values’ be the same thing?
 
Thanks for your help.
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
From: [hidden email] [mailto:jignesh.sutar@...] On Behalf Of J Sutar
Sent:
Monday, December 09, 2013 10:59 AM
To:
Arthur Kramer
Cc:
[hidden email]
Subject:
Re: version 22

 
It's likely to do with the file being saved in Unicode format.
 
http://www-01.ibm.com/support/docview.wss?uid=swg21502287
 
You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.
 
HTH,
Jignesh
 
 
On 9 December 2013 15:42, Arthur Kramer <akramer@...> wrote:
I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.
 
Has anyone else experienced this?
 
 
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
 
Reply | Threaded
Open this post in threaded view
|

Re: version 22

Rick Oliver-3
In reply to this post by Arthur Kramer
http://pic.dhe.ibm.com/infocenter/spssstat/v22r0m0/topic/com.ibm.spss.statistics.help/spss/base/faq_unicode.htm

Rick Oliver
Senior Information Developer
IBM Business Analytics (SPSS)
E-mail: [hidden email]




From:        Arthur Kramer <[hidden email]>
To:        [hidden email],
Date:        12/09/2013 10:17 AM
Subject:        Re: version 22
Sent by:        "SPSSX(r) Discussion" <[hidden email]>




Thanks, Jignesh, but the directions at the link says to look for ‘Character Encoding for Data and Syntax’. That option is not listed on the Options>General drop-down.  Would the ‘Apply locale’s digit grouping format to numeric values’ be the same thing?
 
Thanks for your help.
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
From: [hidden email] [mailto:jignesh.sutar@...] On Behalf Of J Sutar
Sent:
Monday, December 09, 2013 10:59 AM
To:
Arthur Kramer
Cc:
[hidden email]
Subject:
Re: version 22

 
It's likely to do with the file being saved in Unicode format.
 
http://www-01.ibm.com/support/docview.wss?uid=swg21502287
 
You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.
 
HTH,
Jignesh
 
 
On 9 December 2013 15:42, Arthur Kramer <akramer@...> wrote:
I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.
 
Has anyone else experienced this?
 
 
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
 
Reply | Threaded
Open this post in threaded view
|

Re: version 22

Arthur Kramer
In reply to this post by Jon K Peck

Yes. Thank you Jon, and everybody else who sent me information.

 

Rick Oliver, at IBM, sent this link http://pic.dhe.ibm.com/infocenter/spssstat/v22r0m0/topic/com.ibm.spss.statistics.help/spss/base/faq_unicode.htm  which has the instructions, as well.

 

Thank you, again.

 

Arthur Kramer, PhD

Director of Institutional Research

New Jersey City University

 

From: Jon K Peck [mailto:[hidden email]]
Sent: Monday, December 09, 2013 11:30 AM
To: Arthur Kramer
Cc: [hidden email]
Subject: Re: [SPSSX-L] version 22

 

The Options dialog was redesigned for V22, and this setting is now found on the Language tab.

When you first launched V22, you were presented with a dialog that pointed out that Unicode was the default and pointed to a more detailed discussion.  Please look at the help on that topic before deciding whether to stick with code page encodings or move to Unicode.  See the Character Encoding and Locale help topic under Options > Language Options.



Jon Peck (no "h") aka Kim
Senior Software Engineer, IBM
[hidden email]
phone: 720-342-5621




From:        Arthur Kramer <[hidden email]>
To:        [hidden email],
Date:        12/09/2013 09:18 AM
Subject:        Re: [SPSSX-L] version 22
Sent by:        "SPSSX(r) Discussion" <[hidden email]>





Thanks, Jignesh, but the directions at the link says to look for ‘Character Encoding for Data and Syntax’. That option is not listed on the Options>General drop-down.  Would the ‘Apply locale’s digit grouping format to numeric values’ be the same thing?
 
Thanks for your help.
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University
 
From: [hidden email] [[hidden email]] On Behalf Of J Sutar
Sent:
Monday, December 09, 2013 10:59 AM
To:
Arthur Kramer
Cc:
[hidden email]
Subject:
Re: version 22

 
It's likely to do with the file being saved in Unicode format.
 
http://www-01.ibm.com/support/docview.wss?uid=swg21502287
 
You could read/save the file in local encoding which would overcome this but there could potentially be loss of information if file contains characters from foreign languages.
 
HTH,
Jignesh
 
 
On 9 December 2013 15:42, Arthur Kramer <[hidden email]> wrote:
I recently had version 22 loaded onto my computer.  When I read in files created on version 19 the variable field sizes change.  For example, I have an institutional ID field which was seven characters long (because it is seven characters long) is now shown as being 18 characters. Fields that were one character in length are three, or more, characters now. Every field has been changed.  This creates a problem when attempting to join files based on a key variable.
 
Has anyone else experienced this?
 
 
 
Arthur Kramer, PhD
Director of Institutional Research
New Jersey City University