User Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Due to the recently reported Microsoft outage, users may be temporarily unable to access My JMP or experience a delay receiving their verification codes. If you have previously installed JMP on your computer, this outage should not impact your ability to access the software. My JMP services will be restored as soon as Microsoft resolves this issue.
  • Image to Table JMP extension imports single or batch images as data tables. Useful to extract curves from pictures or convert image data to curve data to use in analyses like Functional Data Explorer. Download and install the extension.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
soheila
soheila
Level I

subscripted key not in map{1} in access or evaluation of 'key' , key

Jul 31, 2015 07:06 PM (4062 views)

Hi! i am using JMP to access SAS on demand for soem path analysis. once i hit run it gives me this message: how can i fix this?

subscripted key not in map{1} in access or evaluation of 'key' , key

Thank you!

0 Kudos
1 REPLY 1
Craige_Hales
Super User Craige_Hales
Super User

Re: subscripted key not in map{1} in access or evaluation of 'key' , key

Aug 1, 2015 01:53 PM (3988 views)  |  Posted in reply to message from soheila 07-31-2015

I can't answer the complete question, but I might be able to point you in the right direction:

The message is from JMP's scripting language, JSL.  A "map" is an associative array that can be indexed with character strings (keys), unlike a matrix that can only be indexed with integers.  The "key" is the index to the associative array, and the message means no value has been stored using that key.  If you have the JSL, the variable name you are looking for is "key" (based on the message you got).  Using show(key); in the JSL might tell you what's wrong.

Guessing in the dark: the key that isn't found appears in your data incorrectly.

Craige
0 Kudos

Recommended Articles