You'll likely want to do both: CONFIG.FPW prevents the creation of a new blank resource file. And SET RESOURCE OFF will avoid the hack where someone forces a different config file from the command line (which would let you SET TALK ON and set a _STARTUP program to wedge different behavior into an app...)
And the CONFIG.FPW should be included in your EXE. On Thu, Sep 12, 2013 at 12:07 AM, Fred Taylor <[email protected]> wrote: > As Jeff said, it's too late once you're running. You can still turn it off > in code, but it will still create the resource files if they don't exist. > > SET RESOURCE OFF could be in your code, but RESOURCE=OFF is the only way to > prevent it from creating new files if they don't already exist. > -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ 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/CACW6n4sc=4tgkhaJxDqSd8fpqs13FWBHdV5Hy40G-pLs74K=u...@mail.gmail.com ** 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.
