Warning # 67. Command name: get file

[Ron0z]

The following runs without error:
match files   /file = step1_14   /table = step1_15   /in = continue   /by ClientID  degree.
execute.
(stuff removed)

This also runs without error:
get file step1_15.
(stuff removed)

Note that I am using the same file.  

When I put the two pieces of code together I get a warning:

Warning # 67.  Command name: get file
The document is already in use by another user or process.  If you make
changes to the document they may overwrite changes made by others or your
changes may be overwritten by others.
 

SPSS produces results as expected, but is there a way of suppressing the warning message?

[Maguin, Eugene]

It's very nice that you reported the warning message text. What, very specifically, do you mean by " When I put the two pieces of code together I get a warning:"? What is the exact syntax?

Gene Maguin


-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Ron0z
Sent: Wednesday, February 03, 2016 9:45 PM
To: [hidden email]
Subject: Warning # 67. Command name: get file

The following runs without error:
match files   /file = step1_14   /table = step1_15   /in = continue   /by
ClientID  degree.
execute.
(stuff removed)

This also runs without error:
get file step1_15.
(stuff removed)

Note that I am using the same file.  

When I put the two pieces of code together I get a warning:

/Warning # 67.  Command name: get file
The document is already in use by another user or process.  If you make changes to the document they may overwrite changes made by others or your changes may be overwritten by others./
 

SPSS produces results as expected, but is there a way of suppressing the warning message?




--
View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Warning-67-Command-name-get-file-tp5731429.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

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

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

[David Marso]

Dr. Dr.
It hurts when I do this ;-)
So do it correctly!

get file step1_15.
/* Assumes both files are sorted by ClientID  degree */.
match files   /file = step1_14   /table = */in = continue   /by ClientID  degree.

OR just the first without GET FILE.
-----
Could also look up SET ERRORS OFF.

Ron0z wrote

The following runs without error:
match files   /file = step1_14   /table = step1_15   /in = continue   /by ClientID  degree.
execute.
(stuff removed)

This also runs without error:
get file step1_15.
(stuff removed)

Note that I am using the same file.  

When I put the two pieces of code together I get a warning:

Warning # 67.  Command name: get file
The document is already in use by another user or process.  If you make
changes to the document they may overwrite changes made by others or your
changes may be overwritten by others.
 

SPSS produces results as expected, but is there a way of suppressing the warning message?

[Ron0z]

The following runs without error or warning:

match files   /file = step1_14   /table = step1_15   /in = continue   /by ClientID  degree.
execute.
string ContNextYr (A6).
do if (continue eq 1).
+ compute ContNextYr = 'Cont15'.
else.
+ compute ContNextYr = 'gap'.
end if.
save outfile step2_14
   /drop = continue.




The following also runs error free:

get file step1_15.
string ContNextYr (A6).
compute ContNextYr = 'n/a'.
save outfile step2_15.




However, the following code results in the warning message:

match files   /file = step1_14   /table = step1_15   /in = continue   /by ClientID  degree.
execute.
string ContNextYr (A6).
do if (continue eq 1).
+ compute ContNextYr = 'Cont15'.
else.
+ compute ContNextYr = 'gap'.
end if.
save outfile step2_14
   /drop = continue.



get file step1_15.
string ContNextYr (A6).
compute ContNextYr = 'n/a'.
save outfile step2_15.

[Ron0z]

SET ERRORS OFF is an interesting thing!

Using it results in no messages in the list file, but the syntax window still shows the error.  I wanted to suppress the error from both windows.

SET ERRORS ON is required to return to the status quo, which is just as well.

[David Marso]

Don't know about suppressing from syntax window ;-(

For output, do it like this:

PRESERVE.

SET ERRORS OFF.

do whatever annoying warning thing...

RESTORE.

On Thu, Feb 4, 2016 at 3:16 PM, Ron0z [via SPSSX Discussion] <[hidden email]> wrote:

SET ERRORS OFF is an interesting thing!

Using it results in no messages in the list file, but the syntax window still shows the error.  I wanted to suppress the error from both windows.

SET ERRORS ON is required to return to the status quo, which is just as well.

---

If you reply to this email, your message will be added to the discussion below:

http://spssx-discussion.1045642.n5.nabble.com/Warning-67-Command-name-get-file-tp5731429p5731437.html

To unsubscribe from Warning # 67. Command name: get file, click here.
NAML

[Maguin, Eugene]

OK, Thank you. My suspicion is that the second file (step1_15) remains 'open' or 'attached' within spss as a result of being named in the match files command and causes a conflict when subsequently named on the get command.  I ran this little piece of test code and got warning when I attempted to open tt2. However, if I did a save file command, and then did the get file there was no problem.  You might also try using the Dataset commands to open and close datasets. I don't use them but you can probably figure out how to use them.  Gene Maguin.

data list free / rec x1.
begin data
1,2,2,34,3,27,4,90,5,5,6,7,7,9
end data.
execute.
save outfile='c:\temp\tt1.sav'.

data list free / rec x2.
begin data
2,1,3,56,5,12,6,45,7,4,8,0,9,19
end data.
execute.
save outfile='c:\temp\tt2.sav'.

match files file='c:\temp\tt1.sav'/table='c:\temp\tt2.sav'/by rec.

frequencies x2.

get file='c:\temp\tt2.sav'.




-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Ron0z
Sent: Thursday, February 04, 2016 3:16 PM
To: [hidden email]
Subject: Re: Warning # 67. Command name: get file

SET ERRORS OFF is an interesting thing!

Using it results in no messages in the list file, but the syntax window still shows the error.  I wanted to suppress the error from both windows.

SET ERRORS ON is required to return to the status quo, which is just as well.



--
View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Warning-67-Command-name-get-file-tp5731429p5731437.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

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

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

[Ron0z]

That’s an idea.  I’ll have a play with that.  Actually, DATASETs are nice.  I have used them before. Things can get confusing if there are a lot of them open at one time, but DATASET CLOSE ALL works nicely to keep things tidy.