LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (July 2006)Back to main SPSSX-L pageJoin or leave SPSSX-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 13 Jul 2006 13:56:04 +1000
Reply-To:     Simon Freidin <>
Sender:       "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
From:         Simon Freidin <>
Subject:      Re: execute
Content-type: text/plain; charset=us-ascii; format=flowed

If you're managing a massive database or writing thousands of lines of transformation commands then excessive execute's will give poorer performance.

For everybody else ( = most of us) they are irrelevant, except where forced execution is required, and there are lots of those:

1. more than one missing value statement for the same variables must be separated by execute/procedure or the effect is as if only the last missing value statement exists 2. prior to apply dictionary if the file has been opened but the data is not yet loaded 3. prior to using the results of lag function on a string 4. after write command 5. after print command 6. before 'show n' if case selection will occur 7. when you are using transient system variables in subsequent code ie compute caseno=$casenum.

Having just done a search, I find that I actually use at least one execute in almost every program! :-)

cheers Simon

Research Database Manager and Analyst Melbourne Institute of Applied Economic and Social Research The University of Melbourne Melbourne VIC 3010 Australia New Tel: (03) 8344 2085 New Fax: (03) 8344 2111

Back to: Top of message | Previous page | Main SPSSX-L page