This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
- I wasn't aware the Help menu had trace viewing. Nice.
- I see scads of errors here, many of which say "SEVERE" in the second column, but none of them appear around 1300 when I posted this. There are a series of font-related WARNING entries at 1148. View Log & View Trace appear very similar, except Log has more data about WARNING, and Trace has more data about SEVERE. At least that's what I see at this moment.
- I don't use automagic build. I have only one database open and do "Build All" when I'm done with all the editing I will do that go-round, then I refresh the server from my development template and check it out. I've had a simply mind-boggling amount of trouble with DDE, and one of the things I've discovered is not using automagic build reduces the number of Exception dialogs I get. I prefer doing manual builds, anyway.
- I have seen automagic build turn itself off dozens of times. That's another reason I don't use it ... I can't count how many hours I've wasted trying to figure out some issue, when what's happened is automagic build turned itself off so my code isn't being updated any longer. Doesn't take much of that to be enough. (shrug) I've experienced this up through FP2, which I'm using right now.
- That's why my post indicates either DDE updated inappropriately, or I failed to build it, as opposed to DDE updated inappropriately, or DDE failed to build it. If automagic build were supposed to be on, but turned itself off again, I wouldn't post about a build issue. I'd chalk it up automagic biting me in the rear again and drive on. But I'm pretty sure I did build it, and refresh history on the status bar supported that, so I posted anyway.
- For some reason the *SUPPORT directory contains a whole pile of console* files, all of which contain 1K of ... mess. It's like the logger thinks the file should only be 1k and is doing wrap-around logging, so newer entires appear on top and older ones are one the bottom, but never more than 1K of actual log. I seem to recall I set up some sort of debug logging way back when, for a PMR, and that utterly borked client logging. That's never been addressed. I'd be delighted to have the normal logging back again.
- Just poked around in my notes.ini and don't see anything out of the ordinary, other than an HTTPJVMMaxHeapSize entry, which seems out of place in a client's configuration. There is not one single entry concerning console log file, console log enabling, debug setting, or anything of that nature anywhere, by visual inspection or regexp search. Any ideas what's going on there?
Thanks for your time...
Feedback response number DGIE86GSHL created by ~Holly Zekhipisonnivu on 06/16/2010
Thanks Simon...
Return to top
. . . . Thanks Simon... (~James Brewever... 16.Jun.10) 
