Is this something that might be fixed in sp1?
Before calling SalReportPrint we were setting nErr to 1, meaning "show errors on screen". But then, illogically, we were also passing the flag RPT_PrintNoErrors. In previous versions this contradiction caused no problems. But it seems as if causes TD6.3 to return nErr = 1 from the function, and then hang on exiting (the executable stays in memory).
Simply leaving nErr at 0 before the call solves the problem.
Who is online
Users browsing this forum: [Ccbot] and 0 guests