Running Qdesign/Quick in Debug

[Deskin, Bob]

Any stray environment variables or program parameters? I gather that when
you say it has no relation to the code, this isn't an interpretation thing.
In other words, it's not a case of how QUICK works. Because there are some
cases where there isn't any actual source code the can be attached to what
QUICK is doing.

Bob Deskin              
PowerHouse Web Product Manager and Senior Product Advisor
Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


-----Original Message-----
From: Ronald W. Olenic [mailto:olenicr@dteenergy.com]
Sent: Thursday, October 21, 1999 11:10 AM
To: 'PowerHouse List'
Subject: Running Qdesign/Quick in Debug


When Debug mode was first introduce for QUICK, I thought it was the best
thing since sliced bread(I have no life).  It reduced my debugging time
dramatically.  However on my current system, about half of the screens
where I try to run in debug mode, the code displayed has no relation to
the code being executed.  
I have tried:
   Eliminating all of the nolist options on my use files, 
   Deleting the *.qkd and *.qkl files before compilation
   insuring I am in the same directory where the compiled objects reside
and yet, for some screens it works, and for some it doesn't.

I know there are lots of other ways to debug, (not that any of MY code
would have problems...) but it is such a time saver, it is kind of
frustrating to not be able to use it.

Any(polite) suggestions would be welcome.

Thanks!

Ron Olenic
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.