JMR
VIP Member
I am curious as to exactly where this system function gets its data and how it works.
Here is what I am doing:
- Running UBE A with run-time data selection
- UBE A calls UBE B (which has the same bsvw as UBE A)
- UBE B calls 'Use Data Sel/Seq..' in the Initialize section for the UBE A report and version
Here is what I am seeing:
- When testing it locally, if I enter data selection at run-time it does NOT work (it does not 'see' run-time changes...only the static values that are stored in the version).
- When run on the server, it does pick up the data selection as entered for UBE A ( all works as expected )
- When more than 1 UBE B is running concurrently on the server, it appears that UBE B uses only the last submitted data selection from UBE A ( much like Scheduler works ).
So question #1:
- Does this system function only work on the server?
- It appears as though it gets the selection from latest run (just as Scheduler works)... can anyone confirm this?
Thank you,
Here is what I am doing:
- Running UBE A with run-time data selection
- UBE A calls UBE B (which has the same bsvw as UBE A)
- UBE B calls 'Use Data Sel/Seq..' in the Initialize section for the UBE A report and version
Here is what I am seeing:
- When testing it locally, if I enter data selection at run-time it does NOT work (it does not 'see' run-time changes...only the static values that are stored in the version).
- When run on the server, it does pick up the data selection as entered for UBE A ( all works as expected )
- When more than 1 UBE B is running concurrently on the server, it appears that UBE B uses only the last submitted data selection from UBE A ( much like Scheduler works ).
So question #1:
- Does this system function only work on the server?
- It appears as though it gets the selection from latest run (just as Scheduler works)... can anyone confirm this?
Thank you,