RESOLVED. I discovered a small bug in RB when using weights. If you have a range defined with an empty upper or lower boundary (‘null’ in the syntax below) weighted value will always show up as 0.
However setting the max value to an actual number instead (in this example to 100) solved the problem:
This bug is confirmed. I see it in the source code. In the function pctinrange(q, minvalue, maxvalue), if either minvalue or maxvalue are null, the weighted result doesn't compute. I'll release a fix ASAP.
pctinrange(q, minvalue, maxvalue)
This issue is resolved as of release 1.2.1030 11/23/2015.