Tracy Pearson <[email protected]> wrote: >Allen <[email protected]> wrote: > >>There was mention of using debug to change something and it became >>clear >>again so it's not really any better >>Al >> >>-----Original Message----- >> >> >>If it has been encrypted with ReFox, the right password needs to be >>used to >>decrypt it. I'm sure there is a way to brute force the decryption.
If you run the EXE in the IDE, you can open the Debugger and see code in forms and class libraries. Code in the prgs is not available. If you don't mind not having the line number in your error messages, you can uncheck debug at compile time in the IDE. This prevents seeing code on the debugger. With the right level setting in ReFox, the EXE will not run in the IDE. There are other nuances to be aware of when using that. This only works with VFP 8 & 9, if memory serves. You need to use encrypted runtime files too. Another EXE will not be able to share the code in it. (i.e. Set procedure allows accessing code in a compiled EXE or APP.) YMMV -- Tracy Sent from my Android phone with K-9 Mail. _______________________________________________ Post Messages to: [email protected] 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.
