Includ & GET File Problem

[Juan Pablo Sandoval]

Hi:

I have e GET FILE syntax wich runs fine on it's own but if I invoque it form
a INCLUDE file command it won't run and calls and error as if one of the
first variables on the get command were part of a not recognized command...

Is there an specific format that syntaxes called by and INCLUDE command must
conform, or al least a rule of thumb to avoid such problems???

Regards,

=====================
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

[Richard Ristow]

At 12:39 PM 2/1/2008, Juan Pablo Sandoval wrote:

>I have e GET FILE syntax which runs fine on it's own but if I invoke
>it form a INCLUDE file command it won't run and calls and error as
>if one of the first variables on the get command were part of a not
>recognized command...
>
>Is there an specific format that syntaxes called by and INCLUDE
>command must conform, or al least a rule of thumb to avoid such problems???

There is a specific format. This came up recently; in response, at
06:37 PM 1/29/2008, ViAnn Beadle wrote ("Re: INCLUDE command goof ups"):

>INCLUDE follows batch syntax rules. Batch syntax rules are 1) All
>commands must start in column 1; 2) all continuations to commands
>must start after column 1 3) the command terminator is not required
>to signal the end of a command.
>
>Use the INSERT command instead of the INCLUDE command which provides
>more control.

If following these rules doesn't solve it, post your syntax. (In
fact, when you're inquiring about an error message form syntax, you
should *always* post the syntax, preferably taken from an output
window and including the error message.)

=====================
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

[Oliver, Richard]

INCLUDE files must follow batch processing rules: all commands must begin in the first column of a new line, and all continuation lines must be indented at least one space. Command terminators are optional. The best bet for avoiding confusion is to use the INSERT command instead of INCLUDE.

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Juan Pablo Sandoval
Sent: Friday, February 01, 2008 11:40 AM
To: [hidden email]
Subject: Includ & GET File Problem

Hi:

I have e GET FILE syntax wich runs fine on it's own but if I invoque it form
a INCLUDE file command it won't run and calls and error as if one of the
first variables on the get command were part of a not recognized command...

Is there an specific format that syntaxes called by and INCLUDE command must
conform, or al least a rule of thumb to avoid such problems???

Regards,

=====================
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