Bizarre (and stupid) problem with 17.0 syntax
Locked
12
12
Bizarre (and stupid) problem with 17.0 syntax
 
|
Against my better judgment, I installed Version 17.0 last week. I have syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, but I didn't keep it installed long enough to be sure.
Anyway, this very simple command: SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. Produces this Error Message Error # 5303 in column 114. Text: . A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command has been encountered. Check spelling and punctuation. This command not executed. When I echo the commands to the Log, here's what the program is apparently actually reading: SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . Notice the extra period...it's apparently inserting an additional period which is causing its own error. If I remove "my" period, then the syntax runs without error. Am I missing something here? I'm not going to go through all of my syntax and remove all the periods from my "SAVE" statements, so it may be back to 15.0 again. ====================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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
Although I have already noticed some SPSS 17-problems, I haven't got this
problem. And I already used some old spss 15 syntax files. But your problem is really bizarre.... Francien On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell <[hidden email]> wrote: > Against my better judgment, I installed Version 17.0 last week. I have > syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, > but I didn't keep it installed long enough to be sure. > � > Anyway, this very simple command: > � > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt > Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > � > � > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command has > been > encountered. Check spelling and punctuation. > This command not executed. > � > When I echo the commands to the Log, here's what the program is > actually reading: > � > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt > Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > � > Notice the extra period...it's apparently inserting an additional period > which is causing its own error. If I remove "my" period, then the syntax > runs without error. > � > Am I missing something here? I'm not going to go through all of my syntax > and remove all the periods from my "SAVE" statements, so it may be back > 15.0 again. > � > � > � > � > � > > > > > ====================To manage your subscription to SPSSX-L, send a > 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
In reply to this post by David Futrell
See if this helps. In the syntax window place your cursor after "sav."
Type <enter>. hit <del>until the next line moves up. Art Kendall Social Research Consultants David Futrell wrote: > Against my better judgment, I installed Version 17.0 last week. I have syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, but I didn't keep it installed long enough to be sure. > > Anyway, this very simple command: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > > > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command has been > encountered. Check spelling and punctuation. > This command not executed. > > When I echo the commands to the Log, here's what the program is apparently actually reading: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > > Notice the extra period...it's apparently inserting an additional period which is causing its own error. If I remove "my" period, then the syntax runs without error. > > Am I missing something here? I'm not going to go through all of my syntax and remove all the periods from my "SAVE" statements, so it may be back to 15.0 again. > > > > > > > > > > =================== > 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 > > > ===================== 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
Art Kendall
Social Research Consultants |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by Francien Berndsen
It is bizarre. Fortunately, it's easily fixed. I'll bet there is a space (or more) after the period at the end of your command. If you remove everything after the period, the error should go away.
Jonathan Fry SPSS Inc. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Monday, October 27, 2008 10:43 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Although I have already noticed some SPSS 17-problems, I haven't got this problem. And I already used some old spss 15 syntax files. But your problem is really bizarre.... Francien On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell <[hidden email]> wrote: > Against my better judgment, I installed Version 17.0 last week. I have > syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, > but I didn't keep it installed long enough to be sure. > > Anyway, this very simple command: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt > Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > > > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command has > been > encountered. Check spelling and punctuation. > This command not executed. > > When I echo the commands to the Log, here's what the program is > actually reading: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black Belt > Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > > Notice the extra period...it's apparently inserting an additional period > which is causing its own error. If I remove "my" period, then the syntax > runs without error. > > Am I missing something here? I'm not going to go through all of my syntax > and remove all the periods from my "SAVE" statements, so it may be back > 15.0 again. > > > > > > > > > > ====================To manage your subscription to SPSSX-L, send a > 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 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by David Futrell
I just made a SWAG that you might have period, white space, period in
your syntax. Was one of the characters you deleted another period. Art David Futrell wrote: > Art, > > Thanks for looking a this. That indeed makes the syntax run, but it > falls short of being a real "solution" as it requires me to change my > syntax. > > Is SPSS interpreting the line break as a command end and erroneously > sticking in a "." ? > > > > See if this helps. In the syntax window place your cursor after "sav." > Type <enter>. hit <del>until the next line moves up. > > Art Kendall > Social Research Consultants > > > > ===================== 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
Art Kendall
Social Research Consultants |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by Fry, Jonathan B.
This problem has been reported to SPSS Development, and is described in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. The symptoms initially reported were somewhat different, since the problem was first noticed on the GET FILE command. However, any syntax command with one or more spaces following the terminating period may be affected.
The defect is expected to be resolved in SPSS 17.0.1, which has a tentative release date of December 15, 2008. SPSS Support cannot guarantee what will happen in the future, so I emphasize that this is a tentative release date, and is subject to change. We apologize for any inconvenience. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Fry, Jonathan B. Sent: Monday, October 27, 2008 10:47 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax It is bizarre. Fortunately, it's easily fixed. I'll bet there is a space (or more) after the period at the end of your command. If you remove everything after the period, the error should go away. Jonathan Fry SPSS Inc. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Monday, October 27, 2008 10:43 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Although I have already noticed some SPSS 17-problems, I haven't got this problem. And I already used some old spss 15 syntax files. But your problem is really bizarre.... Francien On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell <[hidden email]> wrote: > Against my better judgment, I installed Version 17.0 last week. I have > syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, > but I didn't keep it installed long enough to be sure. > > Anyway, this very simple command: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > > > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command > has been encountered. Check spelling and punctuation. > This command not executed. > > When I echo the commands to the Log, here's what the program is > actually reading: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > > Notice the extra period...it's apparently inserting an additional > period which is causing its own error. If I remove "my" period, then > the syntax runs without error. > > Am I missing something here? I'm not going to go through all of my > syntax and remove all the periods from my "SAVE" statements, so it may > be back > 15.0 again. > > > > > > > > > > ====================To manage your subscription to SPSSX-L, send a > 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 ===================== 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 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by David Futrell
Hi all,
Bizarre and Stupid! The phase of SPSS is too fast but I doubt(at least my own opinion) of the accuracy. Is there really a need to be fast? If SPSS has problems for small things, how much more for bigger things. I've been an spss users for more than a decade, but I worried of the many negative comments. Negative comments have been occured every release of a new version. I am afraid of this. For those new in this list, you may browse in the listserv such comments. Eins Eins Bernardo <[hidden email]> wrote: Hi all, Bizarre and Stupid! The phase of SPSS is too fast but I doubt(at least my own opinion) of the accuracy. Is there really a need to be fast? If SPSS has problems for small things, how much more for bigger things. I've been an spss users for more than a decade, but I worried of the many negative comments. Negative comments have been occured every release of a new version. I am afraid of this. Eins SPSS Support <[hidden email]> wrote: This problem has been reported to SPSS Development, and is described in Resolution 80177 on the SPSS Support website . The symptoms initially reported were somewhat different, since the problem was first noticed on the GET FILE command. However, any syntax command with one or more spaces following the terminating period may be affected. The defect is expected to be resolved in SPSS 17.0.1, which has a tentative release date of December 15, 2008. SPSS Support cannot guarantee what will happen in the future, so I emphasize that this is a tentative release date, and is subject to change. We apologize for any inconvenience. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Fry, Jonathan B. Sent: Monday, October 27, 2008 10:47 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax It is bizarre. Fortunately, it's easily fixed. I'll bet there is a space (or more) after the period at the end of your command. If you remove everything after the period, the error should go away. Jonathan Fry SPSS Inc. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Monday, October 27, 2008 10:43 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Although I have already noticed some SPSS 17-problems, I haven't got this problem. And I already used some old spss 15 syntax files. But your problem is really bizarre.... Francien On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell wrote: > Against my better judgment, I installed Version 17.0 last week. I have > syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, > but I didn't keep it installed long enough to be sure. > > Anyway, this very simple command: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > > > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command > has been encountered. Check spelling and punctuation. > This command not executed. > > When I echo the commands to the Log, here's what the program is > actually reading: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > > Notice the extra period...it's apparently inserting an additional > period which is causing its own error. If I remove "my" period, then > the syntax runs without error. > > Am I missing something here? I'm not going to go through all of my > syntax and remove all the periods from my "SAVE" statements, so it may > be back > 15.0 again. > > > > > > > > > > ====================To manage your subscription to SPSSX-L, send a > 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 ===================== 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 ===================== 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 ===================== 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 --------------------------------- New Email addresses available on Yahoo! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! --------------------------------- New Email addresses available on Yahoo! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by SPSS Support
Yesterday, I told you all, that I haven't noticed the problem. But... today
I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. Francien On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > This problem has been reported to SPSS Development, and is described in > Resolution 80177 on the SPSS Support website <http://support.spss.com/>. > The symptoms initially reported were somewhat different, since the problem > was first noticed on the GET FILE command. However, any syntax command > with one or more spaces following the terminating period may be affected. > > The defect is expected to be resolved in SPSS 17.0.1, which has a > tentative release date of December 15, 2008. SPSS Support cannot guarantee > what will happen in the future, so I emphasize that this is a tentative > release date, and is subject to change. > > We apologize for any inconvenience. > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of > Fry, Jonathan B. > Sent: Monday, October 27, 2008 10:47 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > It is bizarre. Fortunately, it's easily fixed. I'll bet there is a > (or more) after the period at the end of your command. If you remove > everything after the period, the error should go away. > > Jonathan Fry > SPSS Inc. > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of > Francien Berndsen > Sent: Monday, October 27, 2008 10:43 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Although I have already noticed some SPSS 17-problems, I haven't got this > problem. And I already used some old spss 15 syntax files. > > But your problem is really bizarre.... > > Francien > > > On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell <[hidden email]> > wrote: >> Against my better judgment, I installed Version 17.0 last week. I have >> syntax that I have run under 15.0 for years. It possibly ran 16.0 as > well, >> but I didn't keep it installed long enough to be sure. >> >> Anyway, this very simple command: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >> >> Produces this Error Message >> >> >> Error # 5303 in column 114. Text: . >> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >> has been encountered. Check spelling and punctuation. >> This command not executed. >> >> When I echo the commands to the Log, here's what the program is > apparently >> actually reading: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >> >> Notice the extra period...it's apparently inserting an additional >> period which is causing its own error. If I remove "my" period, then >> the syntax runs without error. >> >> Am I missing something here? I'm not going to go through all of my >> syntax and remove all the periods from my "SAVE" statements, so it may >> be back > to >> 15.0 again. >> >> >> >> >> >> >> >> >> >> ====================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 > > ===================== > 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 > commands to manage subscriptions, send the command INFO REFCARD > > ===================== > 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 > > ===================== > 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
Francien,
It seems that only the last line of any selection is affected. So, the Frequencies command can fail when run by itself, but will be successful when followed by another command. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Tuesday, October 28, 2008 2:50 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Yesterday, I told you all, that I haven't noticed the problem. But... today I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. Francien On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > This problem has been reported to SPSS Development, and is described > in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. > The symptoms initially reported were somewhat different, since the problem > was first noticed on the GET FILE command. However, any syntax > command with one or more spaces following the terminating period may be affected. > > The defect is expected to be resolved in SPSS 17.0.1, which has a > tentative release date of December 15, 2008. SPSS Support cannot guarantee > what will happen in the future, so I emphasize that this is a > tentative release date, and is subject to change. > > We apologize for any inconvenience. > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Fry, Jonathan B. > Sent: Monday, October 27, 2008 10:47 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > It is bizarre. Fortunately, it's easily fixed. I'll bet there is a > (or more) after the period at the end of your command. If you remove > everything after the period, the error should go away. > > Jonathan Fry > SPSS Inc. > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Francien Berndsen > Sent: Monday, October 27, 2008 10:43 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Although I have already noticed some SPSS 17-problems, I haven't got > this problem. And I already used some old spss 15 syntax files. > > But your problem is really bizarre.... > > Francien > > > On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell > <[hidden email]> > wrote: >> Against my better judgment, I installed Version 17.0 last week. I >> have syntax that I have run under 15.0 for years. It possibly ran >> 16.0 as > well, >> but I didn't keep it installed long enough to be sure. >> >> Anyway, this very simple command: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >> >> Produces this Error Message >> >> >> Error # 5303 in column 114. Text: . >> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >> has been encountered. Check spelling and punctuation. >> This command not executed. >> >> When I echo the commands to the Log, here's what the program is > apparently >> actually reading: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >> >> Notice the extra period...it's apparently inserting an additional >> period which is causing its own error. If I remove "my" period, then >> the syntax runs without error. >> >> Am I missing something here? I'm not going to go through all of my >> syntax and remove all the periods from my "SAVE" statements, so it >> may be back > to >> 15.0 again. >> >> >> >> >> >> >> >> >> >> ====================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 > > ===================== > 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 > commands to manage subscriptions, send the command INFO REFCARD > > ===================== > 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 > > ===================== > 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 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
I tested again. You're completely correct.
Thanks, now I now how to avoid it. On Tue, 28 Oct 2008 09:58:17 -0500, SPSS Support <[hidden email]> wrote: > Francien, > > It seems that only the last line of any selection is affected. So, the > Frequencies command can fail when run by itself, but will be successful > when followed by another command. > > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of > Francien Berndsen > Sent: Tuesday, October 28, 2008 2:50 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Yesterday, I told you all, that I haven't noticed the problem. But... > today I just used a syntax made with 17 one week ago and it produces a > similar error. But now with a frequencies command. The strange thing is > that the problem doesn't appear every time I run the syntax. > > So, I'm really glad it will be solved. But, to tell some good news about > 17.0. I really love the totally new syntax editor and 17 is much faster > then spss 16 (not really surprising) and spss 15. > > Francien > > > On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> >> This problem has been reported to SPSS Development, and is described >> in Resolution 80177 on the SPSS Support website > <http://support.spss.com/>. >> The symptoms initially reported were somewhat different, since the > problem >> was first noticed on the GET FILE command. However, any syntax >> command with one or more spaces following the terminating period may be > affected. >> >> The defect is expected to be resolved in SPSS 17.0.1, which has a >> tentative release date of December 15, 2008. SPSS Support cannot > guarantee >> what will happen in the future, so I emphasize that this is a >> tentative release date, and is subject to change. >> >> We apologize for any inconvenience. >> ____________________________________________________________ >> John Bauer >> SPSS Inc. >> Email: [hidden email] >> Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> >> >> >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Fry, Jonathan B. >> Sent: Monday, October 27, 2008 10:47 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> It is bizarre. Fortunately, it's easily fixed. I'll bet there is a > space >> (or more) after the period at the end of your command. If you remove >> everything after the period, the error should go away. >> >> Jonathan Fry >> SPSS Inc. >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Francien Berndsen >> Sent: Monday, October 27, 2008 10:43 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> Although I have already noticed some SPSS 17-problems, I haven't got >> this problem. And I already used some old spss 15 syntax files. >> >> But your problem is really bizarre.... >> >> Francien >> >> >> On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell >> <[hidden email]> >> wrote: >>> Against my better judgment, I installed Version 17.0 last week. I >>> have syntax that I have run under 15.0 for years. It possibly ran >>> 16.0 as >> well, >>> but I didn't keep it installed long enough to be sure. >>> >>> Anyway, this very simple command: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >>> >>> Produces this Error Message >>> >>> >>> Error # 5303 in column 114. Text: . >>> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >>> has been encountered. Check spelling and punctuation. >>> This command not executed. >>> >>> When I echo the commands to the Log, here's what the program is >> apparently >>> actually reading: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >>> >>> Notice the extra period...it's apparently inserting an additional >>> period which is causing its own error. If I remove "my" period, then >>> the syntax runs without error. >>> >>> Am I missing something here? I'm not going to go through all of my >>> syntax and remove all the periods from my "SAVE" statements, so it >>> may be back >> to >>> 15.0 again. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ====================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 >> >> ===================== >> 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 >> >> ===================== >> 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 >> >> ===================== >> 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 > > ===================== > 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 > commands to manage subscriptions, send the command INFO REFCARD > > ===================== > 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by E. Bernardo
Eins,
We release a new version of the SPSS Statistics product each year to better deliver required functionality to our users. We extensively test each release, both internally and externally, and are always qualifying new beta testers. If you (or others on the list) are interested in applying to the beta test program, please send me your contact information. Regards. Kyle Weeks, Ph.D. Director of Product Strategy, SPSS Statistics SPSS Inc. Phone: 1.312.651.3645 / Fax: 1.312.651.3690 [hidden email] www.spss.com SPSS Inc. helps organizations turn data into insight through predictive analytics. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Eins Bernardo Sent: Tuesday, October 28, 2008 1:13 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Hi all, Bizarre and Stupid! The phase of SPSS is too fast but I doubt(at least my own opinion) of the accuracy. Is there really a need to be fast? If SPSS has problems for small things, how much more for bigger things. I've been an spss users for more than a decade, but I worried of the many negative comments. Negative comments have been occured every release of a new version. I am afraid of this. For those new in this list, you may browse in the listserv such comments. Eins Eins Bernardo <[hidden email]> wrote: Hi all, Bizarre and Stupid! The phase of SPSS is too fast but I doubt(at least my own opinion) of the accuracy. Is there really a need to be fast? If SPSS has problems for small things, how much more for bigger things. I've been an spss users for more than a decade, but I worried of the many negative comments. Negative comments have been occured every release of a new version. I am afraid of this. Eins SPSS Support <[hidden email]> wrote: This problem has been reported to SPSS Development, and is described in Resolution 80177 on the SPSS Support website . The symptoms initially reported were somewhat different, since the problem was first noticed on the GET FILE command. However, any syntax command with one or more spaces following the terminating period may be affected. The defect is expected to be resolved in SPSS 17.0.1, which has a tentative release date of December 15, 2008. SPSS Support cannot guarantee what will happen in the future, so I emphasize that this is a tentative release date, and is subject to change. We apologize for any inconvenience. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Fry, Jonathan B. Sent: Monday, October 27, 2008 10:47 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax It is bizarre. Fortunately, it's easily fixed. I'll bet there is a space (or more) after the period at the end of your command. If you remove everything after the period, the error should go away. Jonathan Fry SPSS Inc. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Monday, October 27, 2008 10:43 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Although I have already noticed some SPSS 17-problems, I haven't got this problem. And I already used some old spss 15 syntax files. But your problem is really bizarre.... Francien On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell wrote: > Against my better judgment, I installed Version 17.0 last week. I have > syntax that I have run under 15.0 for years. It possibly ran 16.0 as well, > but I didn't keep it installed long enough to be sure. > > Anyway, this very simple command: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. > > Produces this Error Message > > > Error # 5303 in column 114. Text: . > A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command > has been encountered. Check spelling and punctuation. > This command not executed. > > When I echo the commands to the Log, here's what the program is > actually reading: > > SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black > Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . > > Notice the extra period...it's apparently inserting an additional > period which is causing its own error. If I remove "my" period, then > the syntax runs without error. > > Am I missing something here? I'm not going to go through all of my > syntax and remove all the periods from my "SAVE" statements, so it may > be back > 15.0 again. > > > > > > > > > > ====================To manage your subscription to SPSSX-L, send a > 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 ===================== 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 ===================== 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 ===================== 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 --------------------------------- New Email addresses available on Yahoo! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! --------------------------------- New Email addresses available on Yahoo! Get the Email name you've always wanted on the new @ymail and @rocketmail. Hurry before someone else does! ===================== 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 ===================== 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 |
|
|
In reply to this post by SPSS Support
Couple of glitches that have never been fixed and are still present in
17 plus a new one. When running aggregate in the point and click sometimes the OK button remains grey despite the fact that all required fields are complete. If I go and click off the Number of Cases box and then fill it in again the OK ungrays. Occasionally if I compute some new variables and then go into the select window the new variables are not listed. I actually not sure if this is fixed in 17, as I haven't tried it. Saving the file does not change anything. I have to exit and restart SPSS to get them to appear. The new issue is that I do not seem to be able to copy and paste variable names from Excel. I guess I can just create them in Syntax, but this was convenient. Thanks Matt Matthew Pirritano, Ph.D. Research Analyst IV Medical Services Initiative (MSI) Orange County Health Care Agency (714) 834-3566 ===================== 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 |
|
|
In reply to this post by SPSS Support
And another new issue that is kind of annoying. If I'm at say line
543,765 and I decided to widen the column I'm instantly transported to the top of the data, line 1. I don't think this used to happen. I would have noticed it. Along the same lines as this if I'm looking at VARIABLE 4000 and I decide to change a column width by clicking and dragging on the column I'm again moved all the way to the top. Matt Matthew Pirritano, Ph.D. Research Analyst IV Medical Services Initiative (MSI) Orange County Health Care Agency (714) 834-3566 ===================== 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 |
|
|
Hi Matthew,
Have you informed SPSS Technical Support of these irritations? Let me know if you have not, and I will. Regards, Jason On Thu, Oct 30, 2008 at 6:04 AM, Pirritano, Matthew <[hidden email]> wrote: > And another new issue that is kind of annoying. If I'm at say line > 543,765 and I decided to widen the column I'm instantly transported to > the top of the data, line 1. I don't think this used to happen. I would > have noticed it. Along the same lines as this if I'm looking at VARIABLE > 4000 and I decide to change a column width by clicking and dragging on > the column I'm again moved all the way to the top. > > Matt > > Matthew Pirritano, Ph.D. > Research Analyst IV > Medical Services Initiative (MSI) > Orange County Health Care Agency > (714) 834-3566 > > ===================== > 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 > ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by SPSS Support
What happens if the terminator is on its own line?
E.g. FREQ myvars . I'm using V15 and not excited to move to v17 (yet). Jim Marks Director of Market Research LodgeNet Interactive Corporation 3900 W Innovation St Sioux Falls SD 57107-7002 Phone: 605-988-1616 Fax: 605-988-1506 [hidden email] This e-mail and attached files contain LodgeNet confidential information intended for the exclusive use of the individual(s) to whom addressed. If you are not the intended recipient, please immediately delete this e-mail (and attached files) and treat the information as confidential. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of SPSS Support Sent: Tuesday, October 28, 2008 9:58 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Francien, It seems that only the last line of any selection is affected. So, the Frequencies command can fail when run by itself, but will be successful when followed by another command. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Tuesday, October 28, 2008 2:50 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Yesterday, I told you all, that I haven't noticed the problem. But... today I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. Francien On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > This problem has been reported to SPSS Development, and is described > in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. > The symptoms initially reported were somewhat different, since the problem > was first noticed on the GET FILE command. However, any syntax > command with one or more spaces following the terminating period may be affected. > > The defect is expected to be resolved in SPSS 17.0.1, which has a > tentative release date of December 15, 2008. SPSS Support cannot guarantee > what will happen in the future, so I emphasize that this is a > tentative release date, and is subject to change. > > We apologize for any inconvenience. > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Fry, Jonathan B. > Sent: Monday, October 27, 2008 10:47 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > It is bizarre. Fortunately, it's easily fixed. I'll bet there is a > (or more) after the period at the end of your command. If you remove > everything after the period, the error should go away. > > Jonathan Fry > SPSS Inc. > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Francien Berndsen > Sent: Monday, October 27, 2008 10:43 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Although I have already noticed some SPSS 17-problems, I haven't got > this problem. And I already used some old spss 15 syntax files. > > But your problem is really bizarre.... > > Francien > > > On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell > <[hidden email]> > wrote: >> Against my better judgment, I installed Version 17.0 last week. I >> have syntax that I have run under 15.0 for years. It possibly ran >> 16.0 as > well, >> but I didn't keep it installed long enough to be sure. >> >> Anyway, this very simple command: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >> >> Produces this Error Message >> >> >> Error # 5303 in column 114. Text: . >> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >> has been encountered. Check spelling and punctuation. >> This command not executed. >> >> When I echo the commands to the Log, here's what the program is > apparently >> actually reading: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >> >> Notice the extra period...it's apparently inserting an additional >> period which is causing its own error. If I remove "my" period, then >> the syntax runs without error. >> >> Am I missing something here? I'm not going to go through all of my >> syntax and remove all the periods from my "SAVE" statements, so it >> may be back > to >> 15.0 again. >> >> >> >> >> >> >> >> >> >> ====================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 > > ===================== > 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 > commands to manage subscriptions, send the command INFO REFCARD > > ===================== > 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 > > ===================== > 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 ===================== 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 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
Jim,
Your example as written (without a trailing space following the period) will always run. If there is a space after the terminating period of the last command selected, an extra period will be added by the parser, and the syntax will not be understood. After adding a trailing space to your example, the exact result is: ----------------------------------------------------------------- FREQUENCIES VARIABLES=myvars . . Text: . Command: FREQUENCIES Unrecognized text was found where a variable list was expected. This command not executed. ----------------------------------------------------------------- In summary, if there is no space after the terminating period, there won't be a problem. It doesn't matter whether the terminator is on a line by itself, or the same line as the rest of the command. If the selection includes another command after the one with the extra space, there won't be a problem. The only time there is a problem is when the last terminator of a selection is followed by a trailing space on the same line. ___________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Marks, Jim Sent: Thursday, October 30, 2008 11:37 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax What happens if the terminator is on its own line? E.g. FREQ myvars . I'm using V15 and not excited to move to v17 (yet). Jim Marks Director of Market Research LodgeNet Interactive Corporation 3900 W Innovation St Sioux Falls SD 57107-7002 Phone: 605-988-1616 Fax: 605-988-1506 [hidden email] This e-mail and attached files contain LodgeNet confidential information intended for the exclusive use of the individual(s) to whom addressed. If you are not the intended recipient, please immediately delete this e-mail (and attached files) and treat the information as confidential. -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of SPSS Support Sent: Tuesday, October 28, 2008 9:58 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Francien, It seems that only the last line of any selection is affected. So, the Frequencies command can fail when run by itself, but will be successful when followed by another command. ____________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen Sent: Tuesday, October 28, 2008 2:50 AM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax Yesterday, I told you all, that I haven't noticed the problem. But... today I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. Francien On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > This problem has been reported to SPSS Development, and is described > in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. > The symptoms initially reported were somewhat different, since the problem > was first noticed on the GET FILE command. However, any syntax > command with one or more spaces following the terminating period may be affected. > > The defect is expected to be resolved in SPSS 17.0.1, which has a > tentative release date of December 15, 2008. SPSS Support cannot guarantee > what will happen in the future, so I emphasize that this is a > tentative release date, and is subject to change. > > We apologize for any inconvenience. > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Fry, Jonathan B. > Sent: Monday, October 27, 2008 10:47 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > It is bizarre. Fortunately, it's easily fixed. I'll bet there is a > (or more) after the period at the end of your command. If you remove > everything after the period, the error should go away. > > Jonathan Fry > SPSS Inc. > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Francien Berndsen > Sent: Monday, October 27, 2008 10:43 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Although I have already noticed some SPSS 17-problems, I haven't got > this problem. And I already used some old spss 15 syntax files. > > But your problem is really bizarre.... > > Francien > > > On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell > <[hidden email]> > wrote: >> Against my better judgment, I installed Version 17.0 last week. I >> have syntax that I have run under 15.0 for years. It possibly ran >> 16.0 as > well, >> but I didn't keep it installed long enough to be sure. >> >> Anyway, this very simple command: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >> >> Produces this Error Message >> >> >> Error # 5303 in column 114. Text: . >> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >> has been encountered. Check spelling and punctuation. >> This command not executed. >> >> When I echo the commands to the Log, here's what the program is > apparently >> actually reading: >> >> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >> >> Notice the extra period...it's apparently inserting an additional >> period which is causing its own error. If I remove "my" period, then >> the syntax runs without error. >> >> Am I missing something here? I'm not going to go through all of my >> syntax and remove all the periods from my "SAVE" statements, so it >> may be back > to >> 15.0 again. >> >> >> >> >> >> >> >> >> >> ====================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 > > ===================== > 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 > commands to manage subscriptions, send the command INFO REFCARD > > ===================== > 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 > > ===================== > 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 ===================== 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 ===================== 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 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
This definitely doesn't happen in SPSS 15 (never used 16 enough to know
if it happened there). I understand it can be worked around, but the bigger problem is trying to run old syntax that used to work. Having to search 10,000 lines of code for frequency or save commands with trailing spaces or whatever doesn't sound like much fun. Was this a conscious effort to change stuff or just a bug? If its a bug, will it be fixed in a subsequent update? Graham Wright Campus SPSS Coordinator Brandeis University [hidden email] SPSS Support wrote: > Jim, > > Your example as written (without a trailing space following the period) will always run. > > If there is a space after the terminating period of the last command selected, an extra period will be added by the parser, and the syntax will not be understood. After adding a trailing space to your example, the exact result is: > > ----------------------------------------------------------------- > FREQUENCIES VARIABLES=myvars > . . > > Text: . Command: FREQUENCIES > Unrecognized text was found where a variable list was expected. > This command not executed. > ----------------------------------------------------------------- > > In summary, if there is no space after the terminating period, there won't be a problem. It doesn't matter whether the terminator is on a line by itself, or the same line as the rest of the command. If the selection includes another command after the one with the extra space, there won't be a problem. The only time there is a problem is when the last terminator of a selection is followed by a trailing space on the same line. > > ___________________________________________________________ > > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Marks, Jim > Sent: Thursday, October 30, 2008 11:37 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > What happens if the terminator is on its own line? > > E.g. > > FREQ myvars > . > > I'm using V15 and not excited to move to v17 (yet). > > Jim Marks > Director of Market Research > LodgeNet Interactive Corporation > 3900 W Innovation St > Sioux Falls SD 57107-7002 > Phone: 605-988-1616 > Fax: 605-988-1506 > [hidden email] > > This e-mail and attached files contain LodgeNet confidential information intended for the exclusive use of the individual(s) to whom addressed. If you are not the intended recipient, please immediately delete this e-mail (and attached files) and treat the information as confidential. > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of SPSS Support > Sent: Tuesday, October 28, 2008 9:58 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Francien, > > It seems that only the last line of any selection is affected. So, the Frequencies command can fail when run by itself, but will be successful when followed by another command. > > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Francien Berndsen > Sent: Tuesday, October 28, 2008 2:50 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Yesterday, I told you all, that I haven't noticed the problem. But... today I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. > > So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. > > Francien > > > On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > >> This problem has been reported to SPSS Development, and is described >> in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. >> The symptoms initially reported were somewhat different, since the >> > problem > >> was first noticed on the GET FILE command. However, any syntax >> command with one or more spaces following the terminating period may be affected. >> >> The defect is expected to be resolved in SPSS 17.0.1, which has a >> tentative release date of December 15, 2008. SPSS Support cannot >> > guarantee > >> what will happen in the future, so I emphasize that this is a >> tentative release date, and is subject to change. >> >> We apologize for any inconvenience. >> ____________________________________________________________ >> John Bauer >> SPSS Inc. >> Email: [hidden email] >> Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> >> >> >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Fry, Jonathan B. >> Sent: Monday, October 27, 2008 10:47 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> It is bizarre. Fortunately, it's easily fixed. I'll bet there is a >> > space > >> (or more) after the period at the end of your command. If you remove >> everything after the period, the error should go away. >> >> Jonathan Fry >> SPSS Inc. >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Francien Berndsen >> Sent: Monday, October 27, 2008 10:43 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> Although I have already noticed some SPSS 17-problems, I haven't got >> this problem. And I already used some old spss 15 syntax files. >> >> But your problem is really bizarre.... >> >> Francien >> >> >> On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell >> <[hidden email]> >> wrote: >> >>> Against my better judgment, I installed Version 17.0 last week. I >>> have syntax that I have run under 15.0 for years. It possibly ran >>> 16.0 as >>> >> well, >> >>> but I didn't keep it installed long enough to be sure. >>> >>> Anyway, this very simple command: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >>> >>> Produces this Error Message >>> >>> >>> Error # 5303 in column 114. Text: . >>> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >>> has been encountered. Check spelling and punctuation. >>> This command not executed. >>> >>> When I echo the commands to the Log, here's what the program is >>> >> apparently >> >>> actually reading: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >>> >>> Notice the extra period...it's apparently inserting an additional >>> period which is causing its own error. If I remove "my" period, then >>> the syntax runs without error. >>> >>> Am I missing something here? I'm not going to go through all of my >>> syntax and remove all the periods from my "SAVE" statements, so it >>> may be back >>> >> to >> >>> 15.0 again. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ====================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 >>> >> ===================== >> 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 >> >> ===================== >> 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 >> >> ===================== >> 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 >> > > ===================== > 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 > > ===================== > 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 > > ===================== > 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 > > ===================== > 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 > ===================== 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 |
|
|
In reply to this post by mpirritano
Matthew,
The Aggregate problem that you describe seems to reflect a bug that was filed for SPSS 16 and fixed in SPSS 17.0. I replicated the problem in SPSS 16.0.2 but I cannot replicate it in 17.0. In 17.0, the OK button will be enabled as soon as I enter a variable in the 'Break Variable(s)' box and enter a variable in the 'Summaries of Variables' box and/or check the 'Number of cases' box. If I then click the radio button beside 'Create a new dataset containing only the aggregated variables', then the OK is greyed out but this is because the dataset name has now become a new required field. As soon as I enter a name for the new dataset, the OK is enabled again. The problem regarding newly-computed variables that do not appear in the 'Select IF' dialog was filed for SPSS 16 and has indeed been fixed in SPSS 17. In 16.0.2, the new variable did appear in the main "Select cases" dialog but did not appear in the "Select Cases:IF" dialog. In SPSS 17.0, the new variable appears in both dialogs. The workaround in SPSS 16 was actually much simpler than restarting SPSS. If you clicked the Reset button in the main "Select Cases" dialog before clicking the "If" button, then the new variable would be included in the variable list in the "Select Cases: If" dialog. A colleague in SPSS Technical Support is investigating the issue regarding copy and paste operations with variable names from Excel. A bug has been filed for the problem where the data viewr jumps back to case 1 when you widen a variable 's column width with the cursor. As a workaround, I've found that I can widen the column width in the Variable View without losing my place in the Data View. Suppose that I scrolled down to case 400 and wish to widen the column for variable x. If I click the Variable View button, then click the right side of the cell in the row for Variable X and the 'Columns' column, I can set the number of columns width that I want for the variable. When I click the Data Viewer button, I am still at case 400 and variable X in the data viewer. I hope this helps. David Matheson SPSS Statistical Support -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Pirritano, Matthew Sent: Wednesday, October 29, 2008 1:14 PM To: [hidden email] Subject: issues with 17 Couple of glitches that have never been fixed and are still present in 17 plus a new one. When running aggregate in the point and click sometimes the OK button remains grey despite the fact that all required fields are complete. If I go and click off the Number of Cases box and then fill it in again the OK ungrays. Occasionally if I compute some new variables and then go into the select window the new variables are not listed. I actually not sure if this is fixed in 17, as I haven't tried it. Saving the file does not change anything. I have to exit and restart SPSS to get them to appear. The new issue is that I do not seem to be able to copy and paste variable names from Excel. I guess I can just create them in Syntax, but this was convenient. And another new issue that is kind of annoying. If I'm at say line 543,765 and I decided to widen the column I'm instantly transported to the top of the data, line 1. I don't think this used to happen. I would have noticed it. Along the same lines as this if I'm looking at VARIABLE 4000 and I decide to change a column width by clicking and dragging on the column I'm again moved all the way to the top. Thanks Matt Matthew Pirritano, Ph.D. Research Analyst IV Medical Services Initiative (MSI) Orange County Health Care Agency (714) 834-3566 ===================== 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 ===================== 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 |
Re: Bizarre (and stupid) problem with 17.0 syntax
|
|
In reply to this post by Graham Wright-2
Graham,
Let me emphasize that no one needs to search 10,000 lines of code. Only the last line of the selection needs to be checked. If an entire syntax file is run, and the last command happens to have a trailing space, then only the last command needs to be edited. My reply to the original question on Monday, October 27 was as follows: -------------------------------------------------------- This problem has been reported to SPSS Development, and is described in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. The symptoms initially reported were somewhat different, since the problem was first noticed on the GET FILE command. However, any syntax command with one or more spaces following the terminating period may be affected. The defect is expected to be resolved in SPSS 17.0.1, which has a tentative release date of December 15, 2008. SPSS Support cannot guarantee what will happen in the future, so I emphasize that this is a tentative release date, and is subject to change. We apologize for any inconvenience. -------------------------------------------------------- The description was clarified on Tuesday to include the information that only the last line of the selection being run is affected. ___________________________________________________________ John Bauer SPSS Inc. Email: [hidden email] Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Graham Wright Sent: Thursday, October 30, 2008 1:08 PM To: [hidden email] Subject: Re: Bizarre (and stupid) problem with 17.0 syntax This definitely doesn't happen in SPSS 15 (never used 16 enough to know if it happened there). I understand it can be worked around, but the bigger problem is trying to run old syntax that used to work. Having to search 10,000 lines of code for frequency or save commands with trailing spaces or whatever doesn't sound like much fun. Was this a conscious effort to change stuff or just a bug? If its a bug, will it be fixed in a subsequent update? Graham Wright Campus SPSS Coordinator Brandeis University [hidden email] SPSS Support wrote: > Jim, > > Your example as written (without a trailing space following the period) will always run. > > If there is a space after the terminating period of the last command selected, an extra period will be added by the parser, and the syntax will not be understood. After adding a trailing space to your example, the exact result is: > > ----------------------------------------------------------------- > FREQUENCIES VARIABLES=myvars > . . > > Text: . Command: FREQUENCIES > Unrecognized text was found where a variable list was expected. > This command not executed. > ----------------------------------------------------------------- > > In summary, if there is no space after the terminating period, there won't be a problem. It doesn't matter whether the terminator is on a line by itself, or the same line as the rest of the command. If the selection includes another command after the one with the extra space, there won't be a problem. The only time there is a problem is when the last terminator of a selection is followed by a trailing space on the same line. > > ___________________________________________________________ > > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Marks, Jim > Sent: Thursday, October 30, 2008 11:37 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > What happens if the terminator is on its own line? > > E.g. > > FREQ myvars > . > > I'm using V15 and not excited to move to v17 (yet). > > Jim Marks > Director of Market Research > LodgeNet Interactive Corporation > 3900 W Innovation St > Sioux Falls SD 57107-7002 > Phone: 605-988-1616 > Fax: 605-988-1506 > [hidden email] > > This e-mail and attached files contain LodgeNet confidential information intended for the exclusive use of the individual(s) to whom addressed. If you are not the intended recipient, please immediately delete this e-mail (and attached files) and treat the information as confidential. > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of SPSS Support > Sent: Tuesday, October 28, 2008 9:58 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Francien, > > It seems that only the last line of any selection is affected. So, the Frequencies command can fail when run by itself, but will be successful when followed by another command. > > ____________________________________________________________ > John Bauer > SPSS Inc. > Email: [hidden email] > Tel: +1.312.651.3410 / Fax: +1.312.651.3444 <http://support.spss.com/> > > > > -----Original Message----- > From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf > Of Francien Berndsen > Sent: Tuesday, October 28, 2008 2:50 AM > To: [hidden email] > Subject: Re: Bizarre (and stupid) problem with 17.0 syntax > > Yesterday, I told you all, that I haven't noticed the problem. But... today I just used a syntax made with 17 one week ago and it produces a similar error. But now with a frequencies command. The strange thing is that the problem doesn't appear every time I run the syntax. > > So, I'm really glad it will be solved. But, to tell some good news about 17.0. I really love the totally new syntax editor and 17 is much faster then spss 16 (not really surprising) and spss 15. > > Francien > > > On Mon, 27 Oct 2008 13:31:00 -0500, SPSS Support <[hidden email]> wrote: > >> This problem has been reported to SPSS Development, and is described >> in Resolution 80177 on the SPSS Support website <http://support.spss.com/>. >> The symptoms initially reported were somewhat different, since the >> > problem > >> was first noticed on the GET FILE command. However, any syntax >> command with one or more spaces following the terminating period may be affected. >> >> The defect is expected to be resolved in SPSS 17.0.1, which has a >> tentative release date of December 15, 2008. SPSS Support cannot >> > guarantee > >> what will happen in the future, so I emphasize that this is a >> tentative release date, and is subject to change. >> >> We apologize for any inconvenience. >> ____________________________________________________________ >> John Bauer >> SPSS Inc. >> Email: [hidden email] >> Tel: +1.312.651.3410 / Fax: +1.312.651.3444 >> <http://support.spss.com/> >> >> >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Fry, Jonathan B. >> Sent: Monday, October 27, 2008 10:47 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> It is bizarre. Fortunately, it's easily fixed. I'll bet there is a >> > space > >> (or more) after the period at the end of your command. If you remove >> everything after the period, the error should go away. >> >> Jonathan Fry >> SPSS Inc. >> >> -----Original Message----- >> From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf >> Of Francien Berndsen >> Sent: Monday, October 27, 2008 10:43 AM >> To: [hidden email] >> Subject: Re: Bizarre (and stupid) problem with 17.0 syntax >> >> Although I have already noticed some SPSS 17-problems, I haven't got >> this problem. And I already used some old spss 15 syntax files. >> >> But your problem is really bizarre.... >> >> Francien >> >> >> On Mon, 27 Oct 2008 08:25:23 -0700, David Futrell >> <[hidden email]> >> wrote: >> >>> Against my better judgment, I installed Version 17.0 last week. I >>> have syntax that I have run under 15.0 for years. It possibly ran >>> 16.0 as >>> >> well, >> >>> but I didn't keep it installed long enough to be sure. >>> >>> Anyway, this very simple command: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. >>> >>> Produces this Error Message >>> >>> >>> Error # 5303 in column 114. Text: . >>> A symbol not allowed on the SAVE, XSAVE, or SAVE DIMENSIONS command >>> has been encountered. Check spelling and punctuation. >>> This command not executed. >>> >>> When I echo the commands to the Log, here's what the program is >>> >> apparently >> >>> actually reading: >>> >>> SAVE OUTFILE = 'C:\Documents and Settings\ce90505\My Documents\Black >>> Belt Project\CEM\REP_SURVEY_DATA OCT 08.SAV'. . >>> >>> Notice the extra period...it's apparently inserting an additional >>> period which is causing its own error. If I remove "my" period, then >>> the syntax runs without error. >>> >>> Am I missing something here? I'm not going to go through all of my >>> syntax and remove all the periods from my "SAVE" statements, so it >>> may be back >>> >> to >> >>> 15.0 again. >>> ===================== 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 ===================== 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 |
|
|
In reply to this post by SPSS Support
Matthew,
I mentioned on Thursday that a bug report has been filed for the problem where the data viewer jumps back to case 1 when you widen a variable's column width with the cursor. I've been informed that this defect is expected to be resolved in SPSS 17.0.1, which has a tentative release date of December 15, 2008. David Matheson SPSS Statistical Support -----Original Message----- From: SPSS Support Sent: Thursday, October 30, 2008 1:37 PM To: [hidden email] Subject: RE: issues with 17 Matthew, The Aggregate problem that you describe seems to reflect a bug that was filed for SPSS 16 and fixed in SPSS 17.0. I replicated the problem in SPSS 16.0.2 but I cannot replicate it in 17.0. In 17.0, the OK button will be enabled as soon as I enter a variable in the 'Break Variable(s)' box and enter a variable in the 'Summaries of Variables' box and/or check the 'Number of cases' box. If I then click the radio button beside 'Create a new dataset containing only the aggregated variables', then the OK is greyed out but this is because the dataset name has now become a new required field. As soon as I enter a name for the new dataset, the OK is enabled again. The problem regarding newly-computed variables that do not appear in the 'Select IF' dialog was filed for SPSS 16 and has indeed been fixed in SPSS 17. In 16.0.2, the new variable did appear in the main "Select cases" dialog but did not appear in the "Select Cases:IF" dialog. In SPSS 17.0, the new variable appears in both dialogs. The workaround in SPSS 16 was actually much simpler than restarting SPSS. If you clicked the Reset button in the main "Select Cases" dialog before clicking the "If" button, then the new variable would be included in the variable list in the "Select Cases: If" dialog. A colleague in SPSS Technical Support is investigating the issue regarding copy and paste operations with variable names from Excel. A bug has been filed for the problem where the data viewr jumps back to case 1 when you widen a variable 's column width with the cursor. As a workaround, I've found that I can widen the column width in the Variable View without losing my place in the Data View. Suppose that I scrolled down to case 400 and wish to widen the column for variable x. If I click the Variable View button, then click the right side of the cell in the row for Variable X and the 'Columns' column, I can set the number of columns width that I want for the variable. When I click the Data Viewer button, I am still at case 400 and variable X in the data viewer. I hope this helps. David Matheson SPSS Statistical Support -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Pirritano, Matthew Sent: Wednesday, October 29, 2008 1:14 PM To: [hidden email] Subject: issues with 17 Couple of glitches that have never been fixed and are still present in 17 plus a new one. When running aggregate in the point and click sometimes the OK button remains grey despite the fact that all required fields are complete. If I go and click off the Number of Cases box and then fill it in again the OK ungrays. Occasionally if I compute some new variables and then go into the select window the new variables are not listed. I actually not sure if this is fixed in 17, as I haven't tried it. Saving the file does not change anything. I have to exit and restart SPSS to get them to appear. The new issue is that I do not seem to be able to copy and paste variable names from Excel. I guess I can just create them in Syntax, but this was convenient. And another new issue that is kind of annoying. If I'm at say line 543,765 and I decided to widen the column I'm instantly transported to the top of the data, line 1. I don't think this used to happen. I would have noticed it. Along the same lines as this if I'm looking at VARIABLE 4000 and I decide to change a column width by clicking and dragging on the column I'm again moved all the way to the top. Thanks Matt Matthew Pirritano, Ph.D. Research Analyst IV Medical Services Initiative (MSI) Orange County Health Care Agency (714) 834-3566 ===================== 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 ===================== 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 |
«
Return to SPSSX Discussion
|
1 view|%1 views
| Free forum by Nabble | Edit this page |