cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Choose Language Hide Translation Bar
Monomorphist
Level III

Column (i) << Data Type(Numeric) returns error message

For years, I have a script that I use about 1x a week. Strangely enough, today, it suddenly returned an error message:

 

Argument to Type in access or evaluation of ‘Data Type’, Data Type Numeric ) /*###*/

For(i = 18, i < 103, i = i + 2,
	Column(i) << Data Type(Numeric)
);

I think it's just last week that I've updated to JMP v17.2. Is there a change in the new version? Needless to say, that in the original columns, there could be characters present (such as  "n/a" etc). But that was always the case - and that's why I need to convert format to numeric.

Thanks for advise

 

 

 

 

12 REPLIES 12
hogi
Level XII

Re: Column (i) << Data Type(Numeric) returns error message

Maybe ...

 

hogi_1-1731349420859.png

but this should be solved by using "numeric" as an argument.

Monomorphist
Level III

Re: Column (i) << Data Type(Numeric) returns error message

Good point. I do, of course, have the clear globals and Names default to here commands in the beginning of the script, plus: it worked for years without any issue until suddenly. But with JMP, who knows? I had weirdo behavior of JMP before: eg, a script spits the dummy, when triggered by the green triangle, but works fine when opened (edit command), and then run. Nobody at JMP could ever give me a sensible answer.

Well, yesterday I uninstalled v17.2 and installed the new v18.1. Everything works fine again! No changes made to any of the scripts. Who knows where JMP looks things up, sometimes, that it gets itself so mingled up?!?

hogi
Level XII

Re: Column (i) << Data Type(Numeric) returns error message

By the way ...  the best approach is to install JMP18 in addition to JMP17.

Most things got better - but some featured got removed.
And if you find a bug, it's a good approach to double-check with JMP17 - is it a typo in the code - or a change of the program?

 

Like with the "numeric" - still hard to believe that it did fail. Curious to see if it also fails after starting JMP (17) again.

What could be the reason?

 

 

For the other problem, a wait(0) might fix the issue.

Does the script contain a dt = current data table(); ?
Then try to place the wait(0) in front of it.

Otherwise, just place the wait(0) just after the names default to here(1); and check if this fixes the issue.

Recommended Articles