> This usually works just fine. This chain of events is used for all types of > printing in my system, and it only has a problem with this one particular > two-page report. > > However, on some machines, the report class gets its return value > populated, and therefore erases the tables, before the REPORT FORM ... > command in the separate printing .exe fully completes.
Quite the surprise. It sounds like you have a good semaphone process set up here, and I don't see a flaw in the logic as you've described it. You've eliminated a problem with machines, OS versions and network troubles, it seems like. I'd guess that I'd take a closer look at that one report, as problems only seem to crop up there. Is it possible this report is invoked differently, perhaps with a NOWAIT? As a go-no-go test, try recreating the report and seeing if the problem continues. Quite the stumper. Thanks, Ted. Nope, no NOWAITs. It is the only two-page report the system generates, though. I'd hate to have to recreate the report; it's a complex one with lots of "Print When" statements and precise positioning. But I'll do it if I have to. Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
