difference between SPSS20 and SPSS21

[GFJ van Meurs]

CONTENTS DELETED

The author has deleted this message.

[Bruce Weaver]

Hi Gerard.  I'm still on v20, so no idea.  But this does sound a bit worrying.  Have you applied the available patch(es) for v21?  

Cheers,
Bruce

Meurs, van, Gerard (Intomart GfK) wrote

Dear SPSS-users,

I just ran across an (annoying) difference between the interpretation of macro-calls between SPSS20 and SPSS21.
I use a group of table macros to run custom tables.

In the macro a title is constructed from three arguments given in the call: titel1, titel2 and titel2:

/TITLES TITLE= !CONCAT(!titel1,' ',!titel2) CAPTION= !CONCAT(!titel3).

Although the macro ran smoothly in the previous SPSS-versions, in SPSS21 it occasionally gives me the following message (between <<< and >>>)

<<<
TITLES: Text =. An invalid subcommand, keyword, or option was specified.
Execution of this command stops.
>>>

And when I look in the generated syntax I can see clearly why (part of the generated syntax between <<< and >>>)

<<<
/TITLES TITLE= "a13_01: How likely would you recommend XXXXX to friends, family or colleagues?" "Selection = Knows YYYYY" CAPTION= = "".
>>

The last part should be CAPTION = "", but in some cases this is deformed to CAPTION= = "" , which then returns the error. The strange thing is that in most cases it runs ok.


Any idea what could be the cause of this?



Kind regards, Gerard van Meurs

________________________________

This e-mail (and any attachment) contains confidential and / or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the contents of this e-mail is strictly forbidden.

Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de geadresseerde van dit bericht bent, verzoeken wij u dit bericht te vernietigen zonder van de inhoud kennis te nemen en de inhoud er van niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.

[David Marso]

"Any idea what could be the cause of this?"
Not without your posting the EXACT macro header the relevant internals and sample call?
AFAIK, Nobody has bothered to touch anything inside of MACRO for ages.
I no longer have 20 (2 weeks goes so fast ;-(
so can't be of any help re that.

OTOH:  I used to be the sole SPSS MACRO support person back in the 90-95 era.
Something broke at one point re spurious " " being randomly stuffed into strings.
That was somewhere between ver 5 and 6.  
I finally threatened to quit if they didn't fix it.
MAGIC:  Got fixed in 6.1.4.
Don't know what might be happening now, and really find it hard to believe anybody opened that can of worms (MACRO) in order to break it.

Meurs, van, Gerard (Intomart GfK) wrote

Dear SPSS-users,

I just ran across an (annoying) difference between the interpretation of macro-calls between SPSS20 and SPSS21.
I use a group of table macros to run custom tables.

In the macro a title is constructed from three arguments given in the call: titel1, titel2 and titel2:

/TITLES TITLE= !CONCAT(!titel1,' ',!titel2) CAPTION= !CONCAT(!titel3).

Although the macro ran smoothly in the previous SPSS-versions, in SPSS21 it occasionally gives me the following message (between <<< and >>>)

<<<
TITLES: Text =. An invalid subcommand, keyword, or option was specified.
Execution of this command stops.
>>>

And when I look in the generated syntax I can see clearly why (part of the generated syntax between <<< and >>>)

<<<
/TITLES TITLE= "a13_01: How likely would you recommend XXXXX to friends, family or colleagues?" "Selection = Knows YYYYY" CAPTION= = "".
>>

The last part should be CAPTION = "", but in some cases this is deformed to CAPTION= = "" , which then returns the error. The strange thing is that in most cases it runs ok.


Any idea what could be the cause of this?



Kind regards, Gerard van Meurs

________________________________

This e-mail (and any attachment) contains confidential and / or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the contents of this e-mail is strictly forbidden.

Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de geadresseerde van dit bericht bent, verzoeken wij u dit bericht te vernietigen zonder van de inhoud kennis te nemen en de inhoud er van niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.

Meurs, van, Gerard (Intomart GfK) wrote

Dear SPSS-users,

I just ran across an (annoying) difference between the interpretation of macro-calls between SPSS20 and SPSS21.
I use a group of table macros to run custom tables.

In the macro a title is constructed from three arguments given in the call: titel1, titel2 and titel2:

/TITLES TITLE= !CONCAT(!titel1,' ',!titel2) CAPTION= !CONCAT(!titel3).

Although the macro ran smoothly in the previous SPSS-versions, in SPSS21 it occasionally gives me the following message (between <<< and >>>)

<<<
TITLES: Text =. An invalid subcommand, keyword, or option was specified.
Execution of this command stops.
>>>

And when I look in the generated syntax I can see clearly why (part of the generated syntax between <<< and >>>)

<<<
/TITLES TITLE= "a13_01: How likely would you recommend XXXXX to friends, family or colleagues?" "Selection = Knows YYYYY" CAPTION= = "".
>>

The last part should be CAPTION = "", but in some cases this is deformed to CAPTION= = "" , which then returns the error. The strange thing is that in most cases it runs ok.


Any idea what could be the cause of this?



Kind regards, Gerard van Meurs

________________________________

This e-mail (and any attachment) contains confidential and / or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the contents of this e-mail is strictly forbidden.

Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de geadresseerde van dit bericht bent, verzoeken wij u dit bericht te vernietigen zonder van de inhoud kennis te nemen en de inhoud er van niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.

[Ruben Geert van den Berg]

Interesting post, Gerard!

In a similar vein, a client of mine in Market Research had SaxBasic scripts that used to work in older versions and died silently in V20.

Although that's not supposed to occur, they felt that debugging macros and SaxBasic would eventually come down to "beating a dead horse".

So they decided that the fastest way to make their tools future proof was to simply (ok not always simply) rewrite them in Python. Which made them much shorter, more readable and more flexible as a bonus! But writing the stuff was great, great fun!

If you're unfamiliar with Python, you can create point-click menus that will pass parameters (such as target variables and other options) into functions and run them. You won't even notice that it's actually Python that's doing the work since it's operating under the hood.

HTH,

Ruben

[David Marso]

Gerard, I'm afraid I can't be of any help with CTABLES as I have only BASE for ver 21 .
A very stripped down CTABLES command (one var) would help since when I attempt to run in 11.5 I first need to strip the var names to 8 characters and then CTABLES whines about incorrect variable scale types.  Clean that up and I can verify against 11.5 .  Something very simple and generic is always best in sorting this type of issue.
Jon stated to me off list something about UNICODE MODE in v 21.  Check that.  Again, I don't think things have fundamentally changed in MACRO in 15 years.
The Titles are not all that long compared to some I have seen in the past.

On Sat, May 11, 2013 at 10:53 AM, Meurs, van, Gerard (Intomart GfK) <[hidden email]> wrote:

Hi David,

Thanks for your reaction.

Jon already explained me that the error is probably caused by the fact that my macro calls are much too long (not within the line-limits of SPSS).

And indeed, it certainly has to do with the length of the calls, as it helps to shorten the call, or divide the calls over several lines. But not with length per se, as the 1st call is longer than the 2dn one, whereas the 1st runs ok, the 2dn returns the error.

But to use your macro-expertise, I show you the EXACT-case below (definition and call, between <<< and >>>):

<<<
define tabel1 (VAR1 = !tokens(1)/ VAR2 = !tokens(1)/ VAR3 = !tokens(1)/ TITEL1 = !tokens(1)/ TITEL2 = !tokens(1)/ TITEL3 = !tokens(1)).

CTABLES
 /VLABELS VARIABLES=  Totaal cvar1_B2B cvar2_B2B DISPLAY = Default
 /VLABELS VARIABLES=  !VAR1 Totaal DISPLAY = NONE
 /TABLE !VAR1 [COUNT " " F40.0, COLPCT.COUNT " " PCT40.1, TOTALS[UCOUNT "ongewogen" F40.0, COUNT "gewogen" F40.0]] BY Totaal [C] + cvar1_B2B + cvar2_B2B
 /SLABELS POSITION=ROW
 /CATEGORIES VARIABLES= Totaal cvar1_B2B cvar2_B2B ORDER=A KEY=VALUE EMPTY=INCLUDE
 /CATEGORIES VARIABLES= !VAR1 EMPTY=INCLUDE TOTAL=YES  LABEL='Totaal' POSITION=BEFORE
 /COMPARETEST TYPE=PROP ALPHA=0.05 ADJUST=BONFERRONI ORIGIN=COLUMN INCLUDEMRSETS=YES CATEGORIES=ALLVISIBLE
 /TITLES TITLE= !CONCAT(!titel1,' ', !titel2) CAPTION= !CONCAT(!titel3).
!enddefine.

*
* set MPRINT on to see the generated syntax
*.
SET MPRINT ON.

*
* 2-calls; first runs ok, 2nd with error
*.
tabel1  var1 = a13_02  var2 = a13_02_rec  var3 = x  titel1 = "a13_02: Hoe waarschijnlijk is het dat u de onderstaande xxxxxxxxxxxxx zou aanbevelen aan vrienden, familie en/of collega's? Magazine 111111111111"  titel2 = "Selectie = Indien kent Magazine 111111111111"  titel3 = "test-20-21".
tabel1  var1 = a13_13  var2 = a13_13_rec  var3 = x  titel1 = "a13_13: Hoe waarschijnlijk is het dat u de onderstaande yyyyyyyyyyyyy zou aanbevelen aan vrienden, familie en/of collega's? Magazine 222"  titel2 = "Selectie = Indien kent Magazine 222"  titel3 = "test-20-21".
>>>

Kind regards, Gerard


-----Oorspronkelijk bericht-----
Van: SPSSX(r) Discussion [mailto:[hidden email]] Namens David Marso
Verzonden: vrijdag 10 mei 2013 19:13
Aan: [hidden email]
Onderwerp: Re: difference between SPSS20 and SPSS21

"Any idea what could be the cause of this?"
*Not* without your posting the EXACT macro header the relevant internals and sample call?
AFAIK, Nobody has bothered to touch anything inside of MACRO for ages.
I no longer have 20 (2 weeks goes so fast ;-( so can't be of any help re that.

OTOH:  I used to be the sole SPSS MACRO support person back in the 90-95 era.
Something broke at one point re spurious " " being randomly stuffed into strings.
That was somewhere between ver 5 and 6.
I finally threatened to quit if they didn't fix it.
MAGIC:  Got fixed in 6.1.4.
Don't know what might be happening now, and really find it hard to believe anybody opened that can of worms (MACRO) in order to break it.


Meurs, van, Gerard (Intomart GfK) wrote
> Dear SPSS-users,
>
> I just ran across an (annoying) difference between the interpretation
> of macro-calls between SPSS20 and SPSS21.
> I use a group of table macros to run custom tables.
>
> In the macro a title is constructed from three arguments given in the
> call: titel1, titel2 and titel2:
>
> /TITLES TITLE= !CONCAT(!titel1,' ',!titel2) CAPTION= !CONCAT(!titel3).
>
> Although the macro ran smoothly in the previous SPSS-versions, in
> SPSS21 it occasionally gives me the following message (between <<< and
> >>>)
>
> <<<
> TITLES: Text =. An invalid subcommand, keyword, or option was specified.
> Execution of this command stops.
>>>>
>
> And when I look in the generated syntax I can see clearly why (part of
> the generated syntax between <<< and >>>)
>
> <<<
> /TITLES TITLE= "a13_01: How likely would you recommend XXXXX to
> friends, family or colleagues?" "Selection = Knows YYYYY" CAPTION= = "".
>>>
>
> The last part should be CAPTION = "", but in some cases this is
> deformed to CAPTION= = "" , which then returns the error. The strange
> thing is that in most cases it runs ok.
>
>
> Any idea what could be the cause of this?
>
>
>
> Kind regards, Gerard van Meurs
>
> ________________________________
>
> This e-mail (and any attachment) contains confidential and / or
> privileged information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender immediately
> and destroy this e-mail. Any unauthorised copying, disclosure or
> distribution of the contents of this e-mail is strictly forbidden.
>
> Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de
> geadresseerde van dit bericht bent, verzoeken wij u dit bericht te
> vernietigen zonder van de inhoud kennis te nemen en de inhoud er van
> niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.


Meurs, van, Gerard (Intomart GfK) wrote
> Dear SPSS-users,
>
> I just ran across an (annoying) difference between the interpretation
> of macro-calls between SPSS20 and SPSS21.
> I use a group of table macros to run custom tables.
>
> In the macro a title is constructed from three arguments given in the
> call: titel1, titel2 and titel2:
>
> /TITLES TITLE= !CONCAT(!titel1,' ',!titel2) CAPTION= !CONCAT(!titel3).
>
> Although the macro ran smoothly in the previous SPSS-versions, in
> SPSS21 it occasionally gives me the following message (between <<< and
> >>>)
>
> <<<
> TITLES: Text =. An invalid subcommand, keyword, or option was specified.
> Execution of this command stops.
>>>>
>
> And when I look in the generated syntax I can see clearly why (part of
> the generated syntax between <<< and >>>)
>
> <<<
> /TITLES TITLE= "a13_01: How likely would you recommend XXXXX to
> friends, family or colleagues?" "Selection = Knows YYYYY" CAPTION= = "".
>>>
>
> The last part should be CAPTION = "", but in some cases this is
> deformed to CAPTION= = "" , which then returns the error. The strange
> thing is that in most cases it runs ok.
>
>
> Any idea what could be the cause of this?
>
>
>
> Kind regards, Gerard van Meurs
>
> ________________________________
>
> This e-mail (and any attachment) contains confidential and / or
> privileged information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender immediately
> and destroy this e-mail. Any unauthorised copying, disclosure or
> distribution of the contents of this e-mail is strictly forbidden.
>
> Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de
> geadresseerde van dit bericht bent, verzoeken wij u dit bericht te
> vernietigen zonder van de inhoud kennis te nemen en de inhoud er van
> niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.





-----
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me.
---
"Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis."
Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?"
--
View this message in context: http://spssx-discussion.1045642.n5.nabble.com/difference-between-SPSS20-and-SPSS21-tp5720165p5720170.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

=====================
To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD


This e-mail (and any attachment) contains confidential and / or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the contents of this e-mail is strictly forbidden.

Dit bericht kan vertrouwelijke informatie bevatten. Indien u niet de geadresseerde van dit bericht bent, verzoeken wij u dit bericht te vernietigen zonder van de inhoud kennis te nemen en de inhoud er van niet te gebruiken, niet te kopieren en niet onder derden te verspreiden.

[GFJ van Meurs]

CONTENTS DELETED

The author has deleted this message.