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

---

_______________________________________________

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/F91326DD915A413D93691D9A36F38FF5@jerryfootePC

** 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.

Yes. Depending how your code calls the report it may get added to the

project/executable when next you build it, so be aware of that.

Frank.

Frank Cazabon

Samaan Systems Ltd. - Developing Solutions

www.SamaanSystems.com

Referrals are important to us.

If you know of anyone who would benefit from our services, please contact me. We would appreciate the opportunity to work with them.

On 11/04/2011 02:58 PM, Jerry Foote 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: 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/4DA3536F.5060904@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.

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 <jerryfoote@bellsouth.net> 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: 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/BANLkTi=dqyRaxQ4NGzeLgJvMWaz-oo+wNQ@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.

Jedrry,

Just don't include the report into your project and deploy it into a folder off the applications directory e.g .\Reports. Reference the reports in this folder or use the VFP "set path to ..." and you will load/use the external report.

Make sure however that you don't reference the report directly in your code using a set report to <<report name>> as VFP will automatically include it in the executable. Instead do the following:

cPath = ".\reports\"

...

...

cReport = cPath+"My report"

report form (cReport) .....

...

etc

Dave

-----Original Message-----

From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf Of Jerry Foote

Sent: 11 April 2011 19:59

To: 'ProFox Email List'

Subject: Stand Alone Report Not Included in Project

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: 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/BD031ECABF2B60499200AAB3DBB4A99904EE09@EX-A-FPL.FPL.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.