GREAT news Ben, thank you!!
We should forward this to an SPSS-users list :-)
frans
On 5/6/23 03:02, Ben Pfaff wrote:
I just added this feature: PSPP now allows matching string variables
to have different widths on ADD FILES, MATCH FILES, and UPDATE.
On Wed, Mar 25, 2015 at 7:59 AM Alan Mead
I just added this feature: PSPP now allows matching string variables
to have different widths on ADD FILES, MATCH FILES, and UPDATE.
On Wed, Mar 25, 2015 at 7:59 AM Alan Mead wrote:
>
> On 3/25/2015 8:48 AM, Frans Houweling wrote:
>
> Hi,
> quoting the manual on combining files:
>
> When more t
I see. I wasn't thinking about a table join where a string variable
wouldn't be affected. (Are we 100% certain that the string variable
wouldn't ever be affected? I don't commonly use table joins...)
I think it would be helpful for the programmers to have some short
syntax examples that illustrat
On 26/03/2015 13:00, Alan Mead wrote:
By "I don't think the widest variable should be saved" what exactly do
you mean? If I have email A32 in one file and email A31 in a second
file, if the final merged file has email A31 then one or more email will
be truncated by one character, which means dat
By "I don't think the widest variable should be saved" what exactly do
you mean? If I have email A32 in one file and email A31 in a second
file, if the final merged file has email A31 then one or more email will
be truncated by one character, which means data will be lost. For some
people and some
I don't think the widest variable should be saved - the same old rules
should be followed (eg. in MATCH, if the var is already present leave it
alone). Point is, in 99% of cases the incompatible-width vars are
completely irrelevant for the MATCH at hand, which will fail only
because a feeding f
On 3/26/2015 3:59 AM, ftr wrote:
> So this means that the programs that produce the CSV files produce
> output with different string variable width ?
> This is due to the programs or to the people that use the progs ?
>
> In general, when you import text files you fix the variable width in
> the DA
On 25/03/2015 17:25, Alan Mead wrote:
On 3/25/2015 10:00 AM, ftr wrote:
Frans,
I don't understand why you don't change the variable width for your
string variables. This seems the most easiest way for everyone.
Cheers,
ftr
If you have dozens of variables in dozens of files, it's not "easy
On 3/25/2015 10:00 AM, ftr wrote:
Frans,
I don't understand why you don't change the variable width for your
string variables. This seems the most easiest way for everyone.
Cheers,
ftr
If you have dozens of variables in dozens of files, it's not "easy" to
fix this problem.
I find this mos
Great John! Let's enhance ...
On 25/03/2015 16:32, John Darrington wrote:
On Wed, Mar 25, 2015 at 04:25:20PM +0100, Frans Houweling wrote:
Well, existing SPSS code will not break on PSPP, but the proposed
and hoped-for superior PSPP code will definitely break on SPSS.
S
On Wed, Mar 25, 2015 at 04:25:20PM +0100, Frans Houweling wrote:
Well, existing SPSS code will not break on PSPP, but the proposed
and hoped-for superior PSPP code will definitely break on SPSS.
So maybe there should be some sort of SET STRICT compatibility
option.
On 25/03/2015 15:59, Alan Mead wrote:
I agree completely! And I don't think it would break any reasonable
existing SPSS code for SPSS to silently make the string length in the
combined file of the equal to the longest of the strings, which would
prevent any data loss.
-Alan
Well, existi
Frans,
I don't understand why you don't change the variable width for your
string variables. This seems the most easiest way for everyone.
Cheers,
ftr
On 25/03/2015 14:48, Frans Houweling wrote:
Hi,
quoting the manual on combining files:
When more than one input file contains a variable wit
On 3/25/2015 8:48 AM, Frans Houweling wrote:
Hi,
quoting the manual on combining files:
When more than one input file contains a variable with a given name,
those variables must all have the same type (numeric or string) and,
*for string variables, the same width*.
For me the same width limi
14 matches
Mail list logo
