Select ProcedureCode1 beginswith “J”
or ProcedureCode2 beginswith “J”
or ProcedureCode3 beginswith “J”
or ProcedureCode4 beginswith “J”
or ProcedureCode5 beginswith “J”
Using the Ω gets an error that the field does not exist.
My experiments show using a lineitemΩ in a select formula seems to only check the currently active field. If that field is a line item it will only check that field. If the current field is not one of the desired line item fields it will return an error that the field does not exist. Bug or feature…you tell me.
The Ω suffix does not expand to multiple fields. Instead, it allows you to use a single formula for multiple line items. So the formula
QtyΩ*PriceΩ
will work no matter what line item field is active (and only if a line item field is active). So if the currently active field is Item4, the formula above will be interpreted as:
Qty4*Price4
In your original code, you used:
Select ProcedureCodeΩ beginswith “J”
If you are currently in field ProcedureCode7, this will be interpreted as if it was:
Select ProcedureCode7 beginswith “J”
But if you are currently in the field Address, the result will be an error, because there is no current line item field.
I did try the lineitemarray( but with 30,000 records it was terribly slow compared to
Select ProcedureCode1 beginswith “J”
or ProcedureCode2 beginswith “J”
or ProcedureCode3 beginswith “J”
or ProcedureCode4 beginswith “J”
or ProcedureCode5 beginswith “J”
This is pretty quick; I had simply suspected I could make it faster still with Select ProcedureCodeΩ beginswith “J”.