![build exe in foxpro 2.6 build exe in foxpro 2.6](http://foxcentral.net/microsoft/NETforVFPDevelopers_Chapter01_files/image001.jpg)
_GENXTAB = GETFILE('FXP', "Where is genxtab?") I've found this helpful to answer this question and others.
![build exe in foxpro 2.6 build exe in foxpro 2.6](https://i3.ytimg.com/vi/PGItsK-5xP4/hqdefault.jpg)
In FPW 2.6, determining what the CONFIG.FPW is can be accomplished by adding the "About FoxPro." bar to a menu. The problem might be that in production the CONFIG.FPW file being used is not the same as the one you're using or the file is in a different location. If you've compiled GENXTAB into your project that would explain why it works now. >Do you know how I can get the executable file to know that? create an application or an executable (.exe) file instead of numerous.
BUILD EXE IN FOXPRO 2.6 WINDOWS
Obviously, when I run at command line, the executable file doesn't know what is _GENXTAB. FoxPro 2.6 - FoxPro for MS - DOS Windows - Basic Tutorial and Sample programs. I solve the problem although I still don't understand the reason. >Anyone knows what is the problem? I am stuck. But no thermometer or report comes out and when I get out of the form, it comes out with 'LOCATE QUERY1.DBF'. Normally, I would see the thermometer followed by the report. >As I said, it worked fine when I ran my problem within Foxpro environment but once I ran executable from windows, it wouldn't work (for example, use Start-run or create a program item in win3.11). In other word, if a cursor is the input, a cursor will be the output. The program will create the same type of output as input. You'll find a description of the allowable parameter list.
BUILD EXE IN FOXPRO 2.6 CODE
You might also take a look at the actual program code in GENXTAB.PRG. >Are you sure that your query (in production) is returning records? I'd add IF _TALLY > 0.ENDIF around the call to the crosstab generator. >When you wish to execute the program, use: >Naturally, the directory should reflect the actual current location of the file. Decompilers literally take apart a compiled executable file (APP, EXE, or DLL) and reproduce the source code of the application. This is the case with FoxPro and Visual FoxPro. You can initialize this in your CONFIG.FPW file with: Decompilers have been around as long as compilers. In this case, you should have a copy of the compiled program (FXP file) that's pointed to by the _GENXTAB system variable. >You don't necessary need to include the program in your project. >I patched my genxtab using the file downloaded from MS. It seems to be some setup that needs to be done. If I ran the executable file in the integrated environment, it worked fine.
![build exe in foxpro 2.6 build exe in foxpro 2.6](https://windows-cdn.softpedia.com/screenshots/DBISAM-viewer_1.png)
However When I distributed it using the distribution kit (make exe), the executable couldn't run the report properly. When I ran from foxpro 2.6 integrated environment, it was working fine. >I have a report generated from a genxtab result.