Best Approach to Open SQL Max Selection Length

[former_member221827]

Hi All,

I'm writing a report that needs to compare orders against a subset of order data in an external system. A complex report has already been written to retrieve the data from the external system based on search criteria. I am ideally wanting to submit this report from my own and not have to reinvent the wheel, but I'm concerned on the select option memory limitation.

When my report is started it gets a list of orders based on user criteria and I want to pass that list of orders as the select options of the second report which retrieves data from an external system. I'm concerned that this could lead to short dumps when too many orders are passed into the select option of the second report. Is there a good way to handle this beyond incorporating the code of the second report into my own?

In all the threads I've read I've only seen answers stating that the limitation exists, but I've not seen any nice solutions. I've considered batching the report calls or trying to condense the select option statement putting in ranges when applicable.

Thanks much!

-Chris

[joachimrees1]

Hey Chris,

can you change that "complex report" that already exists?

Then maybe you could move the retrieval of the data to a global class (or a function module) and re-use that in the new report you write?

best

Joachim

[former_member221827]

That is what I ended up doing. I copied and changed the "complex report" to simplify it and add my own logic. It wasn't ideal from a time constraint / effort constraint, but was the best option I found.

Thank you for the input.