There seems to be a problem with FindText when searching a 
string that is longer than 500 bytes.  The code below 
reproduces the error.  It was interesting to note that the 
500 limitation also seemed to apply when I tried to assign 
DummyStr a literal value that was greater than 500 bytes 
and got a compile error.  That is why there are two TESET's 
to assign DummyStr below.

Thanks, Mark


<TEDECLARE var DummyStr text 30000>
<TESET DummyStr 
= "CNA,CNB,CNC,CND20,CND21,CND22,CND23,CND24,CND25,CND26,CND
27,CND28,CND29,CND30,CND31,CND32,CND33,CND34,CND3511,">
<TESET DummyStr = DummyStr 
+ "CND3519,CND3523,CND3524,CND3531,CND3532,CND3533,CND3534,C
ND3535,CND3536,CND3537,CND3541,CND3542,CND3543,CND3544,CND35
45,CND3546,CND3547,CND3548,CND3549,CND3552,CND3553,CND3554,C
ND3555,CND3556,CND3559,CND3561,CND3562,CND3563,CND3564,CND35
65,CND3566,CND3567,CND3568,CND3569,CND3571,CND3572,CND3575,C
ND3577,CND3578,CND3579,CND3581,CND3582,CND3585
 

Verified that FindText has this limit--easy fix to move to 
the configured MaximumStringSize.

Have also found where the expression parser has the same 
limit...also have bumped this to MaximumStringSize.

Fix to these both will be available later today.

Note that you should be able to use the data="" attribute 
in the variable definition to fully initialize, also the 
use of a variable named constant.DummyStr would work very 
well--if you have multiple cases, then maybe multiple 
constant. variables would the work well.

A mix would be to have a variable that is session-based be 
a holder, and then a number of constant. variables provide 
the contents of that variable in a TESet.

That's great about the fix!  Thanks for the other info too 
although the string that caused me to discover the 
limitation is dynamically generated and I just was making a 
trivial example to reproduce the error so I shouldn't need 
to use the constants or the initialization but I will keep 
your recommendations in mind for the future.

Thanks, Mark