Just exclude the report from the project. To state the obvious (because I often get in trouble when I don't), when you send the report files to the customer site, be sure it is in a place where the executable will find it, such as the same directory as the executable (if that was the "Start in" directory for the application), or use a good old-fashioned config.fpw file and set the PATH to the directory containing the external report(s).
In my applications, I always made indirect references to the report names in the report handler. That way, I had an easy choice whether to use external or internal report files. OTOH, I had to manually add "internal" reports to the Project. K On Mon, Apr 11, 2011 at 1:58 PM, Jerry Foote <[email protected]> wrote: > Can I add a report to the customer site that has all information for report > generation in the BeforeOpen code section and then just place it where the > program can find it with out including it in project, and only vfp9 runtime > on machine? > > Thanks Jerry > > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ 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.
