Any changes made to the working file since 17-AUG-2007 15:19:58 have been
Locked
Any changes made to the working file since 17-AUG-2007 15:19:58 have been
 
|
Hello SPSSX colleagues,
I have been encountering this error message -- View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Any-changes-made-to-the-working-file-since-17-AUG-2007-15-19-58-have-been-tp4962800p4962800.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 |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
|
I can't see anything when I click on the
Nabble.com link. However, I have gotten this message when I've tried
to merge files (add variables) and the non-active dataset is supposed to
be a keyed table but either isn't sorted in order of the key variable or
has more than one case with the same key variable. It basically aborts
the merge and reverts to the last saved version of the file. Does
that match your situation?
From: spsstaiwan <[hidden email]> To: [hidden email] Date: 11/03/2011 08:48 PM Subject: Any changes made to the working file since 17-AUG-2007 15:19:58 have been Sent by: "SPSSX(r) Discussion" <[hidden email]> Hello SPSSX colleagues, I have been encountering this error message -- View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Any-changes-made-to-the-working-file-since-17-AUG-2007-15-19-58-have-been-tp4962800p4962800.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 |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
|
Dear Martha,
Thank you very much for your reply. You are right, and thanks so much for confirming that this is not because of any bug. It is indeed related to sorting/merging files, mainly cause my key variable is a string variable, and there are some many-to-many search/merge situation that occurred....Will need to find the correct way to sort the string variables to avoid the error message. Thank you once again and have a good weekend. serena |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
Serena
If there are the same number of cases in each file and your cases in both files are in the same case order, merging shouldn't be a problem. Do they have a case ID? If not you should create one by something like: compute serial = $casenum. That way you can keep track of your cases. As a check on strings, have you tried using AUTORECODE (page 229 of the syntax reference guide obtained from Help) to convert your strings to numeric? A frequency count can then pick up slight variations in the original strings such as typos and extra spaces which may need to be corrected if you are using them as sorting keys. John F Hall [hidden email] www.surveyresearch.weebly.com -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of spsstaiwan Sent: 04 November 2011 03:36 To: [hidden email] Subject: Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been Dear Martha, Thank you very much for your reply. You are right, and thanks so much for confirming that this is not because of any bug. It is indeed related to sorting/merging files, mainly cause my key variable is a string variable, and there are some many-to-many search/merge situation that occurred....Will need to find the correct way to sort the string variables to avoid the error message. Thank you once again and have a good weekend. serena -- View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Any-changes-made-to-the-workin g-file-since-17-AUG-2007-15-19-58-have-been-tp4962812p4962871.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 |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
|
In reply to this post by spsstaiwan
Hello.
I had the same problem with you which GET FILE='C:\Users\personal\Desktop\intern\Accident\new data spss\accident.sav'. DATASET NAME DataSet1 WINDOW=FRONT. MATCH FILES /FILE=* /TABLE='C:\Users\personal\Desktop\intern\Accident\new data spss\injury.sav' /BY ReportNumber. EXECUTE. File #2 KEY: 02022013000210 >Error # 5131 >Duplicate key on a TABLE file. Each case on a TABLE file in MATCH FILES must >be uniquely identified by the BY variables. >Execution of this command stops. Any changes made to the working file since 15-APR-2016 15:51:29 have been lost. The time now is 15:56:29. DISPLAY DICTIONARY. Can you help me how to fixed this problem? Thank you. |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
Administrator
|
The Error message could hardly be more explicit!!! You have a duplicate KEY in the TABLE file and it even gives you the value in question. Please inspect your data and resolve the issue by deciding which one of the possibly several records you wish to retain. There indeed may be more than one problematic value and the current just reports the first one. Consider: GET FILE 'C:\Users\personal\Desktop\intern\Accident\new data spss\injury.sav' . DATASET NAME rawdata. SORT CASES BY ReportNumber . DATASET DECLARE weirdones. AGGREGATE OUTFILE weirdones/ BREAK ReportNumber / COUNT=N. DATASET ACTIVATE weirdones. SELECT IF COUNT GT 1. /* Display aberrant keys */. LIST. MATCH FILES /FILE rawdata / TABLE weirdones / BY ReportNumber . SELECT IF COUNT GT 1. /* Display case level data with aberrant keys */. LIST. Make sense???? ---
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me. --- "Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis." Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?" |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
|
I've had this error pop up when I have not carefully sorted both files in ascending order. If there are no duplicates in the key variable the problem may be the sort order. (And, through this, I have discovered that Excel and SPSS do not handle some characters the same way when sorting!)
Kirsten Kirsten L. Rewey, Ph.D. Quantitative Analyst Minnesota Department of Education 1500 Highway 36 West Roseville, MN 55113 651.582.8638 | [hidden email] -----Original Message----- From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of David Marso Sent: Friday, April 15, 2016 6:27 AM To: [hidden email] Subject: Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been The Error message could hardly be more explicit!!! You have a duplicate KEY in the TABLE file and it even gives you the value in question. Please inspect your data and resolve the issue by deciding which one of the possibly several records you wish to retain. There indeed may be more than one problematic value and the current just reports the first one. Consider: GET FILE 'C:\Users\personal\Desktop\intern\Accident\new data spss\injury.sav' . DATASET NAME rawdata. SORT CASES BY ReportNumber . DATASET DECLARE weirdones. AGGREGATE OUTFILE weirdones/ BREAK ReportNumber / COUNT=N. DATASET ACTIVATE weirdones. SELECT IF COUNT GT 1. /* Display aberrant keys */. LIST. MATCH FILES /FILE rawdata / TABLE weirdones / BY ReportNumber . SELECT IF COUNT GT 1. /* Display case level data with aberrant keys */. LIST. Make sense???? --- nuraslisa aiza wrote > Hello. > I had the same problem with you which > > GET > FILE='C:\Users\personal\Desktop\intern\Accident\new data > spss\accident.sav'. > DATASET NAME DataSet1 WINDOW=FRONT. > MATCH FILES /FILE=* > /TABLE='C:\Users\personal\Desktop\intern\Accident\new data > spss\injury.sav' > /BY ReportNumber. > EXECUTE. > File #2 > KEY: 02022013000210 > >>Error # 5131 >>Duplicate key on a TABLE file. Each case on a TABLE file in MATCH >>FILES >>be uniquely identified by the BY variables. >>Execution of this command stops. > > Any changes made to the working file since 15-APR-2016 15:51:29 have > been lost. > The time now is 15:56:29. > DISPLAY DICTIONARY. > > > > > Can you help me how to fixed this problem? > Thank you. ----- Please reply to the list and not to my personal email. Those desiring my consulting or training services please feel free to email me. --- "Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis." Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?" -- View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Any-changes-made-to-the-working-file-since-17-AUG-2007-15-19-58-have-been-tp4962812p5731940.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 |
|
|
You should not assume that the sort order produced by Excel for strings is the same as in Statistics. Statistics follows the Unicode standard for sorting, but Excel does some things differently. Things such as upper/lower case order, placement of accented characters, the Spanish ll, mixed writing systems (e. g., Hebrew and roman characters) may be handled differently. On Fri, Apr 15, 2016 at 7:25 AM, Rewey, Kirsten (MDE) <[hidden email]> wrote: I've had this error pop up when I have not carefully sorted both files in ascending order. If there are no duplicates in the key variable the problem may be the sort order. (And, through this, I have discovered that Excel and SPSS do not handle some characters the same way when sorting!) |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
Administrator
|
In reply to this post by Kirsten.Rewey
I don't believe an incorrectly sorted file will invoke this error. You will get a different error
>Error # 5130 >File out of order. All the files in MATCH FILES must be in non-descending >order on the BY variables. Use SORT CASES to sort the file. >Execution of this command stops. It will also identify the first incidence of collation error. Please construct a simple example which will reproduce the DUPLICATE KET error with a non duplicate key in a mis-sorted situation? --
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me. --- "Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis." Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?" |
Re: Any changes made to the working file since 17-AUG-2007 15:19:58 have been
|
|
Thank you for the suggestion. I will try to fix it.. On Friday, April 15, 2016 10:20 PM, David Marso [via SPSSX Discussion] <[hidden email]> wrote:
I don't believe an incorrectly sorted file will invoke this error. You will get a different error
>Error # 5130 >File out of order. All the files in MATCH FILES must be in non-descending >order on the BY variables. Use SORT CASES to sort the file. >Execution of this command stops. It will also identify the first incidence of collation error. Please construct a simple example which will reproduce the DUPLICATE KET error with a non duplicate key in a mis-sorted situation? --
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me. --- "Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis." Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?" If you reply to this email, your message will be added to the discussion below:
http://spssx-discussion.1045642.n5.nabble.com/Any-changes-made-to-the-working-file-since-17-AUG-2007-15-19-58-have-been-tp4962812p5731943.html
To unsubscribe from Any changes made to the working file since 17-AUG-2007 15:19:58 have been, click here. NAML |
«
Return to SPSSX Discussion
|
1 view|%1 views
| Free forum by Nabble | Edit this page |