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

[#1]

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

[#2]

I don't remember there being such issues, but I cannot access JMP17.2 currently. This script does work in JMP18.1 though

Names Default To Here(1); 

open("$SAMPLE_DATA/Big Class.jmp");

For(i = 1, i <= N Cols(dt), i++,
	Column(i) << Data Type(Numeric);
);

Based on Scripting Index the argument should be a string (<< Data Type("Numeric") but it seems to work fine (and JMP uses non-string versions when it generates the script with << set data type).

[#3]

Tried as string ("numeric") - no success. Same error message. By the way, this isn't the only script that fails at this command line, others do, too, since the update.

Where do you get 18.1? I've checked for update last week (because of one of my others threads that got suddenly popular, and 18.1 was recommended), but only got 17.2 (and tells me that I have the latest version). And now my scripts don't work anymore....! 

[#4]

This example works in 17.2.

[#5]

My misread of the issue......response deleted

[#6]

Since when? Runs for years with () ! By the way, I've tried other scripts with the same arguments. They all stop and give me error message now. Tens of scripts that worked for years!

[#7]

I still have access to 17.2.  I created a test table and executed your exact script on it.  It worked without error, changing every other column to numeric and replacing the "hi" string with a missing value.

[#8]

This is utterly bizarre. Would you be willing to try the script in the attached? It doesn't work in my version (but should, in my eyes?!?)

[#9]

Strange, indeed.  I ran the script on the test table using JMP 17.2.0 and had no problem.

[#10]

Ok. This means it isn't a matter of the script, nor the table, nor the software version. Conflicts somewhere else, deep inside.....

Well, at least I found V18 in my software depot. Will try new install, then.