Another memory lapse on my part... ;-) I still think ASSERTS are way better than SET STEP as you can define logical conditions that give you the opportunity to invoke the debugger on demand.
-- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ken Dibble Sent: Wednesday, October 08, 2014 11:33 AM To: [email protected] Subject: RE: Extreme Case of PRG File Corruption? >I'd highly recommend using ASSERTS for this kind of stuff instead of >SET STEP. ASSERTS are ignored in the runtime environment so you avoid >feature not supported errors in your EXE while still enjoying dev >debugging on demand. ASSERTS and TRY...CATCH were some of the best >things ever added to the product, imho. SET STEP no longer throws an error in the runtime environment. I think that was changed in VFP 7 (or possibly 8). Thanks for all the help! Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04423C5D793D1@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
