On 4/17/07, Ken Dibble <[EMAIL PROTECTED]> wrote: > > For all the folks who responded in this vain: > > The performance issue was actually the least important of my three reasons; > I wouldn't have adopted the separate printing .exe strategy just for that. > The printer spool and potential data corruption issues were far more > significant. >
The Golden Rule of Consulting: Things are the way they are because they got that way. Starting a discussion with "That's a screwy way to do things" doesn't help a lot. Let's not get all defensive/offensive about what's been done. There likely was a good reason for it. A better start is "here we are; how do we proceed?" Sometimes the answer is "rip it all out and start all over again," but nowhere often as I hear consultants suggest that. Now, back on track: it occurs on multiple machines and with different OSes and doesn't seem to be a configuration thing. It does seem to be isolated to the one two-page report. What's unique about that report? Can you try to create another report that also shows the behavior? Is this problem in production and hard for you to catch? -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ 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.
