Including report forms in exe

I have a VFP (9.0) exe that contains a lot of report forms. Even when
I include the report forms in the reports section of the project I get
a message 'File not found' when you run the exe. I even included
specific pathing for the call
REPORT FORM (gcPath + "reportname") to print noconsole
and I still get the error.
If the report forms are placed in the directory with the exe they work
ok.
Is there something special that needs to be done to make this work
correctly. I don't want all of these frx's sitting in the exe
directory.

Jim Czebiniak

trw7at
Thu Feb 09 10:42:19 CST 2006

Jim Czeb seemed to utter in news:1139496722.700878.121100
@g47g2000cwa.googlegroups.com:

> I have a VFP (9.0) exe that contains a lot of report forms. Even when
> I include the report forms in the reports section of the project I get
> a message 'File not found' when you run the exe. I even included
> specific pathing for the call
> REPORT FORM (gcPath + "reportname") to print noconsole
> and I still get the error.
> If the report forms are placed in the directory with the exe they work
> ok.
> Is there something special that needs to be done to make this work
> correctly. I don't want all of these frx's sitting in the exe
> directory.

Are the report files excluded from the EXE? Check if there
is a little circle with a slash through it next to the
report names in the Project Manager. If so, right click
and select "Include" from the pop-up menu.

-- TRW
_______________________________________
t r w 7
at
i x dot n e t c o m dot c o m
_______________________________________

Leemi
Thu Feb 09 11:04:55 CST 2006

Hi Jim:

What you are doing should work. Are the report files excluded, which means
they are not built into the project? You want the file Included so that
they are built into the project and then the resulting exe.


I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003


>I have a VFP (9.0) exe that contains a lot of report forms. Even when
>I include the report forms in the reports section of the project I get
>a message 'File not found' when you run the exe. I even included
>specific pathing for the call
>REPORT FORM (gcPath + "reportname") to print noconsole
>and I still get the error.
>If the report forms are placed in the directory with the exe they work
>ok.
>Is there something special that needs to be done to make this work
>correctly. I don't want all of these frx's sitting in the exe
>directory.

>Jim Czebiniak

Matthew
Thu Feb 09 11:05:00 CST 2006

Do not include path information to report files when you use REPORT FORM, IE
don't do this:

REPORT FORM (gcPath + "reportname") ...

do this:

REPORT FORM "reportname"

If the reports are in a subdirectory, change the VFP path to include that
subdirectory. And, as Tim suggested, make sure the reports are in the
project and not excluded.

"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
news:1139496722.700878.121100@g47g2000cwa.googlegroups.com...
>I have a VFP (9.0) exe that contains a lot of report forms. Even when
> I include the report forms in the reports section of the project I get
> a message 'File not found' when you run the exe. I even included
> specific pathing for the call
> REPORT FORM (gcPath + "reportname") to print noconsole
> and I still get the error.
> If the report forms are placed in the directory with the exe they work
> ok.
> Is there something special that needs to be done to make this work
> correctly. I don't want all of these frx's sitting in the exe
> directory.
>
> Jim Czebiniak
>

Tom
Thu Feb 09 11:25:31 CST 2006

Jim, i dont use the Full path either for my Report form statements.

but one thing i have found, if the reports are no in the Directory the
Project is, or where the .exe is being built from it will give you trouble.

maybe try to compile everything in the same dir.
Tom

"Jim Czeb" wrote:

> I have a VFP (9.0) exe that contains a lot of report forms. Even when
> I include the report forms in the reports section of the project I get
> a message 'File not found' when you run the exe. I even included
> specific pathing for the call
> REPORT FORM (gcPath + "reportname") to print noconsole
> and I still get the error.
> If the report forms are placed in the directory with the exe they work
> ok.
> Is there something special that needs to be done to make this work
> correctly. I don't want all of these frx's sitting in the exe
> directory.
>
> Jim Czebiniak
>
>

Matthew
Thu Feb 09 12:10:30 CST 2006

I have never put reports in the directory the project is in, nor have I put
them where the exe is built from. Simply put them in a subdirectory, set a
path to that subdirectory, and reports should work fine. I've done it this
way for over 15 years, never had a problem.

"Tom" <Tom@discussions.microsoft.com> wrote in message
news:C28FBFCA-5339-4F9B-8230-A78A7D53774D@microsoft.com...
> Jim, i dont use the Full path either for my Report form statements.
>
> but one thing i have found, if the reports are no in the Directory the
> Project is, or where the .exe is being built from it will give you
> trouble.
>
> maybe try to compile everything in the same dir.
> Tom
>
> "Jim Czeb" wrote:
>
>> I have a VFP (9.0) exe that contains a lot of report forms. Even when
>> I include the report forms in the reports section of the project I get
>> a message 'File not found' when you run the exe. I even included
>> specific pathing for the call
>> REPORT FORM (gcPath + "reportname") to print noconsole
>> and I still get the error.
>> If the report forms are placed in the directory with the exe they work
>> ok.
>> Is there something special that needs to be done to make this work
>> correctly. I don't want all of these frx's sitting in the exe
>> directory.
>>
>> Jim Czebiniak
>>
>>

John
Thu Feb 09 13:18:27 CST 2006

Same here. Never had a problem doing it this way.
The only problem I have is modifing reports on the client side. The report
will run fine, but if I issue a modify report, it always brings up a blank
report.
On the client side, my path is set to \\pos\cashregister,
\\pos\cashregister\reports, etc.... It is like the path is there, but
foxpro will not go over the network to modify it.
John.




"Matthew L Reed" <nousenetspam at dead ice dot us> wrote in message
news:uc$#fZaLGHA.1312@TK2MSFTNGP09.phx.gbl...
> I have never put reports in the directory the project is in, nor have I
put
> them where the exe is built from. Simply put them in a subdirectory, set a
> path to that subdirectory, and reports should work fine. I've done it this
> way for over 15 years, never had a problem.
>
> "Tom" <Tom@discussions.microsoft.com> wrote in message
> news:C28FBFCA-5339-4F9B-8230-A78A7D53774D@microsoft.com...
> > Jim, i dont use the Full path either for my Report form statements.
> >
> > but one thing i have found, if the reports are no in the Directory the
> > Project is, or where the .exe is being built from it will give you
> > trouble.
> >
> > maybe try to compile everything in the same dir.
> > Tom
> >
> > "Jim Czeb" wrote:
> >
> >> I have a VFP (9.0) exe that contains a lot of report forms. Even when
> >> I include the report forms in the reports section of the project I get
> >> a message 'File not found' when you run the exe. I even included
> >> specific pathing for the call
> >> REPORT FORM (gcPath + "reportname") to print noconsole
> >> and I still get the error.
> >> If the report forms are placed in the directory with the exe they work
> >> ok.
> >> Is there something special that needs to be done to make this work
> >> correctly. I don't want all of these frx's sitting in the exe
> >> directory.
> >>
> >> Jim Czebiniak
> >>
> >>
>
>

Jim
Thu Feb 09 14:03:35 CST 2006

Lee, I do not have the report forms excluded in the project.
I do not want the report forms anywhere on the client machine. they
should work the same as screen forms. I don't need to place them in
the folder where the exe is or even on the same computer.
I changed the references to the report form to not include the path as
suggested above.

I still get 'File does not exist' when I attempt to run the report.
One note. The code calling the report forms is not in the project but
is run from a database memo field.
I seem to recall an issue where since the report form is not referenced
anywhere in the code that you need to make a reference to the report
forms in the project.
I tried this.
if .f. = .t. then
report form xxx preview
report form xxx2 preview
etc.
endif

This didn't work either.
Any more suggestions????

Jim Czeb

Matthew
Thu Feb 09 18:51:43 CST 2006

Are you modifying them from within the app, or running VFP on a workstation
with access to the production directories. Your path must not be right, I
can modify reports with unc paths in my path. Works great. Verify the path
really is correct, and the reports really are in that path.


"John G" <nospamoglethorpehardware@earthlink.net> wrote in message
news:O9sFW2aLGHA.3496@TK2MSFTNGP14.phx.gbl...
> Same here. Never had a problem doing it this way.
> The only problem I have is modifing reports on the client side. The
> report
> will run fine, but if I issue a modify report, it always brings up a blank
> report.
> On the client side, my path is set to \\pos\cashregister,
> \\pos\cashregister\reports, etc.... It is like the path is there, but
> foxpro will not go over the network to modify it.
> John.
>
>
>
>
> "Matthew L Reed" <nousenetspam at dead ice dot us> wrote in message
> news:uc$#fZaLGHA.1312@TK2MSFTNGP09.phx.gbl...
>> I have never put reports in the directory the project is in, nor have I
> put
>> them where the exe is built from. Simply put them in a subdirectory, set
>> a
>> path to that subdirectory, and reports should work fine. I've done it
>> this
>> way for over 15 years, never had a problem.
>>
>> "Tom" <Tom@discussions.microsoft.com> wrote in message
>> news:C28FBFCA-5339-4F9B-8230-A78A7D53774D@microsoft.com...
>> > Jim, i dont use the Full path either for my Report form statements.
>> >
>> > but one thing i have found, if the reports are no in the Directory the
>> > Project is, or where the .exe is being built from it will give you
>> > trouble.
>> >
>> > maybe try to compile everything in the same dir.
>> > Tom
>> >
>> > "Jim Czeb" wrote:
>> >
>> >> I have a VFP (9.0) exe that contains a lot of report forms. Even
>> >> when
>> >> I include the report forms in the reports section of the project I get
>> >> a message 'File not found' when you run the exe. I even included
>> >> specific pathing for the call
>> >> REPORT FORM (gcPath + "reportname") to print noconsole
>> >> and I still get the error.
>> >> If the report forms are placed in the directory with the exe they work
>> >> ok.
>> >> Is there something special that needs to be done to make this work
>> >> correctly. I don't want all of these frx's sitting in the exe
>> >> directory.
>> >>
>> >> Jim Czebiniak
>> >>
>> >>
>>
>>
>
>

Jim
Fri Feb 10 06:57:54 CST 2006

>From Jim Czebiniak
I think I have discovered my problem.
Since the code that is calling the report is instantiated at runtime by
doing an execscript(lcCode)
VFP views it as being outside the project.
1. The reports are included in the project.
2. I do not want the frx's located on the client machine.
3. If I call the report from a form in the app it works fine.
Therefore, I know they are in the project, all pathing is fine, etc.
4. If I put the frx and frt's in the folder the exe is in they work
fine. No pathing should be needed.

Is there a way to have code that is defined 'outside the project' to
reference reports in the project.
Having code stored in the database allows for remote and external
modification and versioning of code without building a new exe and
without interrupting those using it.
Any thoughts here???

Jack
Fri Feb 10 08:06:50 CST 2006

That is your problem. Only code included in the exe can see files
that are included in the exe.

What I do is to put a method in the form called "DoCmd":

LPARAMETERS cCmd

&cCmd.

Then to execute a REPORT FORM command I use something like:

cStr = "REPORT FORM ...."
Thisform.DoCmd(cStr)


On 9 Feb 2006 12:03:35 -0800, "Jim Czeb"
<james.czebiniak@pearlcarroll.com> wrote:

>Lee, I do not have the report forms excluded in the project.
>I do not want the report forms anywhere on the client machine. they
>should work the same as screen forms. I don't need to place them in
>the folder where the exe is or even on the same computer.
>I changed the references to the report form to not include the path as
>suggested above.
>
>I still get 'File does not exist' when I attempt to run the report.
>One note. The code calling the report forms is not in the project but
>is run from a database memo field.
>I seem to recall an issue where since the report form is not referenced
>anywhere in the code that you need to make a reference to the report
>forms in the project.
>I tried this.
>if .f. = .t. then
> report form xxx preview
> report form xxx2 preview
> etc.
>endif
>
>This didn't work either.
>Any more suggestions????
>
>Jim Czeb

Matthew
Fri Feb 10 10:28:59 CST 2006

This is very easily done:

SET PROCEDURE TO <executable with embedded reports>
REPORT FORM <report embedded in executable>....

If you SET PROCEDURE to an executable, you have access to the content
embedded in the executable.



"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
news:1139576274.251732.167340@g43g2000cwa.googlegroups.com...
> >From Jim Czebiniak
> I think I have discovered my problem.
> Since the code that is calling the report is instantiated at runtime by
> doing an execscript(lcCode)
> VFP views it as being outside the project.
> 1. The reports are included in the project.
> 2. I do not want the frx's located on the client machine.
> 3. If I call the report from a form in the app it works fine.
> Therefore, I know they are in the project, all pathing is fine, etc.
> 4. If I put the frx and frt's in the folder the exe is in they work
> fine. No pathing should be needed.
>
> Is there a way to have code that is defined 'outside the project' to
> reference reports in the project.
> Having code stored in the database allows for remote and external
> modification and versioning of code without building a new exe and
> without interrupting those using it.
> Any thoughts here???
>

Jack
Fri Feb 10 14:24:05 CST 2006

Can you do this with .app files?

On Fri, 10 Feb 2006 08:28:59 -0800, "Matthew L Reed" <nousenetspam at
dead ice dot us> wrote:

>This is very easily done:
>
>SET PROCEDURE TO <executable with embedded reports>
>REPORT FORM <report embedded in executable>....
>
>If you SET PROCEDURE to an executable, you have access to the content
>embedded in the executable.
>
>
>
>"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
>news:1139576274.251732.167340@g43g2000cwa.googlegroups.com...
>> >From Jim Czebiniak
>> I think I have discovered my problem.
>> Since the code that is calling the report is instantiated at runtime by
>> doing an execscript(lcCode)
>> VFP views it as being outside the project.
>> 1. The reports are included in the project.
>> 2. I do not want the frx's located on the client machine.
>> 3. If I call the report from a form in the app it works fine.
>> Therefore, I know they are in the project, all pathing is fine, etc.
>> 4. If I put the frx and frt's in the folder the exe is in they work
>> fine. No pathing should be needed.
>>
>> Is there a way to have code that is defined 'outside the project' to
>> reference reports in the project.
>> Having code stored in the database allows for remote and external
>> modification and versioning of code without building a new exe and
>> without interrupting those using it.
>> Any thoughts here???
>>
>

Jim
Fri Feb 10 14:32:13 CST 2006

Jack,
Since the code is being run using execscript the form is not known by
the program and thisform is undefined. You get the error 'thisform
can only be used in a method.'

I also tried set procedure to abc.exe but that didn't work either.
Bummer, that looked like the right solution.

Jim

Jack Jackson wrote:
> That is your problem. Only code included in the exe can see files
> that are included in the exe.
>
> What I do is to put a method in the form called "DoCmd":
>
> LPARAMETERS cCmd
>
> &cCmd.
>
> Then to execute a REPORT FORM command I use something like:
>
> cStr = "REPORT FORM ...."
> Thisform.DoCmd(cStr)
>
>
> On 9 Feb 2006 12:03:35 -0800, "Jim Czeb"
> <james.czebiniak@pearlcarroll.com> wrote:
>
> >Lee, I do not have the report forms excluded in the project.
> >I do not want the report forms anywhere on the client machine. they
> >should work the same as screen forms. I don't need to place them in
> >the folder where the exe is or even on the same computer.
> >I changed the references to the report form to not include the path as
> >suggested above.
> >
> >I still get 'File does not exist' when I attempt to run the report.
> >One note. The code calling the report forms is not in the project but
> >is run from a database memo field.
> >I seem to recall an issue where since the report form is not referenced
> >anywhere in the code that you need to make a reference to the report
> >forms in the project.
> >I tried this.
> >if .f. = .t. then
> > report form xxx preview
> > report form xxx2 preview
> > etc.
> >endif
> >
> >This didn't work either.
> >Any more suggestions????
> >
> >Jim Czeb

Matthew
Fri Feb 10 15:56:40 CST 2006

Yes. See my message about how you can't reference a running instance, only
the static physical file on disk.


"Jack Jackson" <jacknospam@pebbleridge.com> wrote in message
news:pgtpu11qk6tif7ckhcdgs1sip9o6ujmo9b@4ax.com...
> Can you do this with .app files?
>
> On Fri, 10 Feb 2006 08:28:59 -0800, "Matthew L Reed" <nousenetspam at
> dead ice dot us> wrote:
>
>>This is very easily done:
>>
>>SET PROCEDURE TO <executable with embedded reports>
>>REPORT FORM <report embedded in executable>....
>>
>>If you SET PROCEDURE to an executable, you have access to the content
>>embedded in the executable.
>>
>>
>>
>>"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
>>news:1139576274.251732.167340@g43g2000cwa.googlegroups.com...
>>> >From Jim Czebiniak
>>> I think I have discovered my problem.
>>> Since the code that is calling the report is instantiated at runtime by
>>> doing an execscript(lcCode)
>>> VFP views it as being outside the project.
>>> 1. The reports are included in the project.
>>> 2. I do not want the frx's located on the client machine.
>>> 3. If I call the report from a form in the app it works fine.
>>> Therefore, I know they are in the project, all pathing is fine, etc.
>>> 4. If I put the frx and frt's in the folder the exe is in they work
>>> fine. No pathing should be needed.
>>>
>>> Is there a way to have code that is defined 'outside the project' to
>>> reference reports in the project.
>>> Having code stored in the database allows for remote and external
>>> modification and versioning of code without building a new exe and
>>> without interrupting those using it.
>>> Any thoughts here???
>>>
>>

Matthew
Fri Feb 10 15:56:14 CST 2006

When you set procedure to an exe, you are not referencing a running instance
of it, but are connecting to the physical file itself. Thisform. etc. will
not work. You only have access to the static contents of the executable,
such as reports. You can instantiate classes, run code, etc., but you are
still not accessing an already running instance.


"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
news:1139603533.123854.102490@o13g2000cwo.googlegroups.com...
> Jack,
> Since the code is being run using execscript the form is not known by
> the program and thisform is undefined. You get the error 'thisform
> can only be used in a method.'
>
> I also tried set procedure to abc.exe but that didn't work either.
> Bummer, that looked like the right solution.
>
> Jim
>
> Jack Jackson wrote:
>> That is your problem. Only code included in the exe can see files
>> that are included in the exe.
>>
>> What I do is to put a method in the form called "DoCmd":
>>
>> LPARAMETERS cCmd
>>
>> &cCmd.
>>
>> Then to execute a REPORT FORM command I use something like:
>>
>> cStr = "REPORT FORM ...."
>> Thisform.DoCmd(cStr)
>>
>>
>> On 9 Feb 2006 12:03:35 -0800, "Jim Czeb"
>> <james.czebiniak@pearlcarroll.com> wrote:
>>
>> >Lee, I do not have the report forms excluded in the project.
>> >I do not want the report forms anywhere on the client machine. they
>> >should work the same as screen forms. I don't need to place them in
>> >the folder where the exe is or even on the same computer.
>> >I changed the references to the report form to not include the path as
>> >suggested above.
>> >
>> >I still get 'File does not exist' when I attempt to run the report.
>> >One note. The code calling the report forms is not in the project but
>> >is run from a database memo field.
>> >I seem to recall an issue where since the report form is not referenced
>> >anywhere in the code that you need to make a reference to the report
>> >forms in the project.
>> >I tried this.
>> >if .f. = .t. then
>> > report form xxx preview
>> > report form xxx2 preview
>> > etc.
>> >endif
>> >
>> >This didn't work either.
>> >Any more suggestions????
>> >
>> >Jim Czeb
>

Jack
Sun Feb 12 10:02:38 CST 2006

Can you assign Thisform to a variable while you are executing in the
form, or use _screen.ActiveForm, to get a form reference?

On 10 Feb 2006 12:32:13 -0800, "Jim Czeb"
<james.czebiniak@pearlcarroll.com> wrote:

>Jack,
>Since the code is being run using execscript the form is not known by
>the program and thisform is undefined. You get the error 'thisform
>can only be used in a method.'
>
>I also tried set procedure to abc.exe but that didn't work either.
>Bummer, that looked like the right solution.
>
>Jim
>
>Jack Jackson wrote:
>> That is your problem. Only code included in the exe can see files
>> that are included in the exe.
>>
>> What I do is to put a method in the form called "DoCmd":
>>
>> LPARAMETERS cCmd
>>
>> &cCmd.
>>
>> Then to execute a REPORT FORM command I use something like:
>>
>> cStr = "REPORT FORM ...."
>> Thisform.DoCmd(cStr)
>>
>>
>> On 9 Feb 2006 12:03:35 -0800, "Jim Czeb"
>> <james.czebiniak@pearlcarroll.com> wrote:
>>
>> >Lee, I do not have the report forms excluded in the project.
>> >I do not want the report forms anywhere on the client machine. they
>> >should work the same as screen forms. I don't need to place them in
>> >the folder where the exe is or even on the same computer.
>> >I changed the references to the report form to not include the path as
>> >suggested above.
>> >
>> >I still get 'File does not exist' when I attempt to run the report.
>> >One note. The code calling the report forms is not in the project but
>> >is run from a database memo field.
>> >I seem to recall an issue where since the report form is not referenced
>> >anywhere in the code that you need to make a reference to the report
>> >forms in the project.
>> >I tried this.
>> >if .f. = .t. then
>> > report form xxx preview
>> > report form xxx2 preview
>> > etc.
>> >endif
>> >
>> >This didn't work either.
>> >Any more suggestions????
>> >
>> >Jim Czeb

Jack
Sun Feb 12 10:05:22 CST 2006

I know that. In my case, I have report forms built as part of the
.app file, but they are called from common classes that are not
included in the .app file. I need some way to access the forms from
the classes. Using SET PROCEDURE TO is much better than the kludge I
am using now. Thanks for the tip.

On Fri, 10 Feb 2006 13:56:40 -0800, "Matthew L Reed" <nousenetspam at
dead ice dot us> wrote:

>Yes. See my message about how you can't reference a running instance, only
>the static physical file on disk.
>
>
>"Jack Jackson" <jacknospam@pebbleridge.com> wrote in message
>news:pgtpu11qk6tif7ckhcdgs1sip9o6ujmo9b@4ax.com...
>> Can you do this with .app files?
>>
>> On Fri, 10 Feb 2006 08:28:59 -0800, "Matthew L Reed" <nousenetspam at
>> dead ice dot us> wrote:
>>
>>>This is very easily done:
>>>
>>>SET PROCEDURE TO <executable with embedded reports>
>>>REPORT FORM <report embedded in executable>....
>>>
>>>If you SET PROCEDURE to an executable, you have access to the content
>>>embedded in the executable.
>>>
>>>
>>>
>>>"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
>>>news:1139576274.251732.167340@g43g2000cwa.googlegroups.com...
>>>> >From Jim Czebiniak
>>>> I think I have discovered my problem.
>>>> Since the code that is calling the report is instantiated at runtime by
>>>> doing an execscript(lcCode)
>>>> VFP views it as being outside the project.
>>>> 1. The reports are included in the project.
>>>> 2. I do not want the frx's located on the client machine.
>>>> 3. If I call the report from a form in the app it works fine.
>>>> Therefore, I know they are in the project, all pathing is fine, etc.
>>>> 4. If I put the frx and frt's in the folder the exe is in they work
>>>> fine. No pathing should be needed.
>>>>
>>>> Is there a way to have code that is defined 'outside the project' to
>>>> reference reports in the project.
>>>> Having code stored in the database allows for remote and external
>>>> modification and versioning of code without building a new exe and
>>>> without interrupting those using it.
>>>> Any thoughts here???
>>>>
>>>
>

Matthew
Mon Feb 13 16:09:09 CST 2006

Back in the good old days when we sent updates out on floppy disks, we would
break apps apart into multiple .app files, and set procedure to each one of
them. Each .app was floppy disk size or smaller, and contained reports,
forms, etc., all the stuff we needed. There is no significant difference
between putting everything in one large exe/app, or setting procedure to a
bunch of smaller exe/app files.

"Jack Jackson" <jacknospam@pebbleridge.com> wrote in message
news:t1nuu1hs7ennt729buops713t1ng9ksq1s@4ax.com...
>I know that. In my case, I have report forms built as part of the
> .app file, but they are called from common classes that are not
> included in the .app file. I need some way to access the forms from
> the classes. Using SET PROCEDURE TO is much better than the kludge I
> am using now. Thanks for the tip.
>
> On Fri, 10 Feb 2006 13:56:40 -0800, "Matthew L Reed" <nousenetspam at
> dead ice dot us> wrote:
>
>>Yes. See my message about how you can't reference a running instance, only
>>the static physical file on disk.
>>
>>
>>"Jack Jackson" <jacknospam@pebbleridge.com> wrote in message
>>news:pgtpu11qk6tif7ckhcdgs1sip9o6ujmo9b@4ax.com...
>>> Can you do this with .app files?
>>>
>>> On Fri, 10 Feb 2006 08:28:59 -0800, "Matthew L Reed" <nousenetspam at
>>> dead ice dot us> wrote:
>>>
>>>>This is very easily done:
>>>>
>>>>SET PROCEDURE TO <executable with embedded reports>
>>>>REPORT FORM <report embedded in executable>....
>>>>
>>>>If you SET PROCEDURE to an executable, you have access to the content
>>>>embedded in the executable.
>>>>
>>>>
>>>>
>>>>"Jim Czeb" <james.czebiniak@pearlcarroll.com> wrote in message
>>>>news:1139576274.251732.167340@g43g2000cwa.googlegroups.com...
>>>>> >From Jim Czebiniak
>>>>> I think I have discovered my problem.
>>>>> Since the code that is calling the report is instantiated at runtime
>>>>> by
>>>>> doing an execscript(lcCode)
>>>>> VFP views it as being outside the project.
>>>>> 1. The reports are included in the project.
>>>>> 2. I do not want the frx's located on the client machine.
>>>>> 3. If I call the report from a form in the app it works fine.
>>>>> Therefore, I know they are in the project, all pathing is fine, etc.
>>>>> 4. If I put the frx and frt's in the folder the exe is in they work
>>>>> fine. No pathing should be needed.
>>>>>
>>>>> Is there a way to have code that is defined 'outside the project' to
>>>>> reference reports in the project.
>>>>> Having code stored in the database allows for remote and external
>>>>> modification and versioning of code without building a new exe and
>>>>> without interrupting those using it.
>>>>> Any thoughts here???
>>>>>
>>>>
>>