$TRANSCRIPT_LOG_FILE

Hi Roger,

Probably I am telling you nothing new, but even I am sometimes puzzled with the $transcript_logfile behaviour. I even remember a while ago Uniface created transcript logfiles with the name NONE…

According to the documentation : the transcript window is still created when there is a reason to show it. With $transcript_logfile  set, the window normally closes automatically once the logging has been written to the file. It only stays open when something goes wrong. The docs mention an error in the assignment file or a network error as examples.

So the apps where you do see the window most likely ran into a problem. One thing to check: if several apps or processes use the same c:\temp\transcript.log, they can get in each other's way. Try adding %p to the file name, so that each process writes its own log file:

[SETTINGS]
$TRANSCRIPT_LOG_FILE=c:\temp\transcript_%p.log

See: https://docs.rocketsoftware.com/bundle/uniface2_104/page/topics/$transcript_log_file_ttr1665702707353.html

Hi
I understand this
With $transcript_logfile  set, the window normally closes automatically once the logging has been written to the file. It only stays open when something goes wrong.

that the transcript-window is viewable during the session but if the transcript window is ok written to file,  it is closed  as you close the application.

My problem is that sometimes I see the transcript-window and sometimes not, although the  
$transcript_log_file=c:\temp\transcript.log
is set.
Do I understand this wrong or are there some other parameters affecting this, eg “$putmess_log_file” and/or $ioprint??

Hi, 
As far as I know, there must be a reason for Uniface to create the transcript window. That are things like network errors, license messages and config errors. 
Where I use $ioprint = 127 for instance I see quite a lot of messages in the transcript window about files that can;t be found.