Thanks Christof, I appreciate. We'll try that and get back here with the result. It may take a couple of days though.
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/ Le 15/03/12 10:43, Christof Wollenhaupt a écrit : >> Project includes *.prg having #include *.h with #DEFINE constants, >> compile into *.fxp and *.fxp run fine in VFP IDE. >> >> Once built into a .exe, the same *.fxp throw errors for seeing constants >> as unknown variables. >> > The project manager and the COMPILE command use different approaches of > resolving include files, especially when nested include files or different > directories are involved. The safest approach is to put include files into > the same directory as the PRG and ensure that CURDIR() is the project > directory when you rebuild the project and compile PRGs. Also make sure > that SET PATH does not point to any other source code directory outside the > project directory. > > To nail down your particular issue go to www.sysinternals.com and download > Process Monitor. Set the filter for path to contain your include file and > rebuild the project in VFP. You should see which file the project manager > picked. Likely one with the same name but without these constants. > > Christof > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] 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/[email protected] ** 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.
