It’s working fine for me; however, we did just update the logging component so it might have a glitch in there somewhere.
First, is the old EL file read-only? It looks like the logging component isn’t updating read-only files. If read-write… Open Help|About and type “bug” and you should get a harmless error message. Click OK and then check for the updated file where you’re expecting it. If you’re still not seeing what you expect check the General page in Options. Is Toad’s application data directory set to the path you expect?
From: kornelis.abe [mailto:firstname.lastname@example.org]
Sent: Monday, September 07, 2015 5:46 AM
Subject: [Toad for Oracle - Beta Discussion Forum] Errorlog file not being written?
Errorlog file not being written?
Thread created by kornelis.abe
I’m a bit hesitant to ask; it’s probably something pretty stupid on my side
It seems that either the errorlog file (Toad.el) is not being written/updated, or it has moved to a different location and I fail to find it…
I expected to find Toad.el (after Toad crashed) in C:\Users\abek\AppData\Roaming\Dell\Toad for Oracle\12.8 beta
but the file I found was from last Friday (according to Windows) and even older (according to content).
I checked the Toad.ini file, found no clue.
Without the errorlog file, Dell development of course cannot be expected to do anything about my Toad crashing from time to time…
Any help is appreciated.
Thanks in advance,
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
this post as spam/abuse.