"Feature Not Available" Error Message for Report Command 2

[sipos]

Hi all,
since 1997, i used foxpro 2.6 dos to create several small program for my company. Usually i use "FOXPROX myprog.app" to start my program, and it's doing fine.

now, i'm trying to compile myprog.app into full standalone extended executable file using Distribution Kit, because it much easier to deploy to new client. Everything is work fine except command "REPORT myrep.frx". This command always create "Feature Not Available" error. i try to compile it to compact extended exe file and the error msg is still visible.

Is this happened because my Distribution Kid has error?
or is this bug on DK FPD 2.6?

thanks

 

[JRB-Bldr]

Let us understand your issue better.
You are not encountering this error message during the EXE Build?
Instead you are encountering the message during when the EXE executes.
Correct?

If you are you saying that when your EXE executes and encounters the command REPORT myrep.frx you get the error message?

As a first guess, you should modify the command line to

REPORT [B]FORM[/B] myrep.frx

Next I would look into the Report Form itself to see if there are any commands or other UDF's which might exist within it which are not available to the EXE.

Next you might want to 'hack' into the Report Form's FRX file to eliminate any default printer settings which might exist.

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[sipos]

Oops ... yes, the correct statement is "REPORT FORM myreport.frx", but it is my typo-mistake sorry about that.

the real issue is that

statement "REPORT FORM myreport.frx" is working correctly when it is executed inside FOXPROX.EXE, but if I build the statement into working standalone executable, the "Feature Not Available" error shows up.

 

[TamarGranor]

Are you, by any chance, referencing all your reports indirectly, either with name expressions or macros? If so, make sure there's at least one place (even if it's after IF .F.) where you use REPORT FORM with an actual file name. I have a vague recollection about things not getting built into the EXE if they're not used.

Tamar

 

[sipos]

oke, thanks ... i think it becuase dereferencing and macros