We are trying to use VB 5 to start BO 4.x, run a report, and pass a set of parms to a filter in the report. The DB is Oracle.
A variable, myVarforNumbers, awaits in the filter. We pass is a string like “465,454,354”, which should work, followed by the ForceCompute sub to the report. The problem is, the report (which uses the InList function) only seems to accept the first parm, not the set. Any help…?
Thanks,
Chris
Listserv Archives (BOB member since 2002-06-25)
Yep, I strugged with that one for days on a job I did a few months ago. Seems that there’s something in the way the @variable syntax works that only makes it work way or the other, but not both. I was able to code the @variable to work with one value by doing one thing, and i was able to code it differently to work with multiple values. I was not able to code it work both ways at the same time.
Sorry, but I don’t remember exactly how the syntax looks each way. It has something to do with whether there are single quotes if I remember rightly. If there are single quotes, it works for multiple values but not one, or vice versa. It was too long ago…
The workaround we used was to code it to work with multiple values, and then make sure that there were always multiple values in the vars file. If the conditions called for only a single value, we had the front-end app repeat that value so that the @variable syntax would work correctly.
Hope that helps.
Regards,
Paul
Listserv Archives (BOB member since 2002-06-25)