Hallo Thomas,

Guten Morgen.

I'm puzzled.

Do I understand right:
You have a small exe that you use for modi rep
this one runs perfectly

My code does not work for you
?


I have tested my code with NOENVIRONMENT PROTECTED SAVE, with or without SET PATH TO JUSTPATH(_REPORTBUILDER)

All what is changed is that I receive sometimes an errormessage "Alias not found", sometimes not.
The preview works fine with Reportbehaviour 80
The "Print" option from popup menu now prints

I have set up an vanilla VFP 9, later SP1 - nothing is changed.

You mentioned that for you SET PATH has some influence
can you please confirm that

SET PATH TO JUSTPATH(_REPORTBUILDER)

SET REPORTBEHAVIOR 90
CREATE CURSOR cur1 (c1 c(10))
INSERT INTO cur1 VALUES ('1')
INSERT INTO cur1 VALUES ('2')
INSERT INTO cur1 VALUES ('3')
*REPORT FORM e:\se\temp\modrep.frx preview
SET RESOURCE OFF
lcFRX = ADDBS(JUSTPATH(SYS(16)))+'modrep.frx'
MODIFY REPORT (lcFRX) NOENVIRONMENT SAVE PROTECTED
</pre
runs for you and
<pre>
*SET PATH TO JUSTPATH(_REPORTBUILDER)

SET REPORTBEHAVIOR 90
CREATE CURSOR cur1 (c1 c(10))
INSERT INTO cur1 VALUES ('1')
INSERT INTO cur1 VALUES ('2')
INSERT INTO cur1 VALUES ('3')
*REPORT FORM e:\se\temp\modrep.frx preview
SET RESOURCE OFF
lcFRX = ADDBS(JUSTPATH(SYS(16)))+'modrep.frx'
MODIFY REPORT (lcFRX) NOENVIRONMENT SAVE PROTECTED

not?

If it is that way, can you share your code? I'm lost.


Agnes

>Hi Agnes,
>
>at the time I only see one difference between your approach and the one that I am working with.
>My call is like this:
>
>

> MODIFY REPORT (m.vFile) NOENVIRONMENT PROTECTED SAVE
>

>
>Although our customers get access to create/modify individuals reports, we never save the dataenvironment with the default report and it will always run in protected mode. BTW the MODI REPO is called from within a small exe which receives just one parameter and that's the frx including the path. If the parameter can be validated, there are some SET commands like path, reportbehavior and sysmenu and then the above mentioned modi repo.
>Looking at your code, to me it isn't obvious why it doesn't behave the way it should. Oh, and we don't use foxuser.dbf...
>