On Tuesday, April 08, 2008 9:49 AM Richard Kaye wrote:
>BTW I'd consider using ASSERTS instead of SET STEP ON. Avoids that
annoying feature not available message in your runtime applications.
>ASSERT .f. MESSAGE [I'm debugging now...] SET CLASSLIB TO
someclass.vcx ADDITIVE oDLL = CreateObject('someclass')
> oDLL.start('someDNS')
The feature not available error does not happen after VFP7 (I am pretty
sure that is the version...). Also, since this job, I have been using a
calling program that starts the debugging. So, I am not putting a SET
STEP ON in the app.
Although Asserts are a good thing to practice as they are used in .NET
testing as well...
David L. Crooks
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** 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.
