- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IR a post dealing with this problem for CVF 6.5 and the poster was referred to Premier Support.
The problem is that reporting to display always works but to a file is iffy.
How did Premier Support resolve this difficulty?
Thanks,
Gerry T.
The problem is that reporting to display always works but to a file is iffy.
How did Premier Support resolve this difficulty?
Thanks,
Gerry T.
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, I get it. If the file wasn't CLOSE(d) before TRACEBACKQQ (TB), the results of a successful TB won't be written to the file. Otherwise, the results of successive TBs are appended to the file until a TB aborts the app.
HTH,
Gerry T.
HTH,
Gerry T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You'll never get referred to Intel Premier Support for a CVF problem - at least not by Intel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The topic "TRACEBACKQQ not sending output to standard error device)" with CVF 6.5 posted 09-14-2004 and 09-24-2004 ended up being referred by you to Intel Premier Support on 09-24-2004.
Ciao,
Gerry T.
Ciao,
Gerry T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, that was my error. I did not notice at the time that it was for CVF. Sorry.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page