Hi,
we are porting sources from bdl 2.5 to 4.01 and are experiencing this error that never showed with 2.50.
Issue happens just when the report was assigned to pipe and the output instruction was never call.
Review the logic is almost impossible due to time and budget.
Probably we can resolve surrounding the finish between WHENEVER ERROR or a TRY CATCH, but maybe there is a better approach.
Anyone knows?
As a sidenote anyone knows what kind of isssues we can stumble upon passing from 2.50 to 4? As a matter of fact is a big leap!
Thankyou.
