Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
#INCLUDE in PRG works differently
Message
From
09/12/2004 22:33:39
James Hansen
Canyon Country Consulting
Flagstaff, Arizona, United States
 
 
To
09/12/2004 21:30:55
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro Beta
Miscellaneous
Thread ID:
00959425
Message ID:
00968208
Views:
7
>You meant FXP here, not FRX, right?
>

Yes, FXP. I've been working to hard on ReportListener stuff lately...

>
>To put your mind at ease: it was this way ever since project manager was introduced, though I don't exactly remember whether that was in FP1.0x or FP2.0.
>
>When you build the project, the generated FXP files are not saved to the disk. They go into the Object memo of the pjx file. IOW, one of these can be wrong while the other still works, even though they are based on the same source. It just depends on the settings at compile time.
>
>This largely differs from what you see in dbf-typed program files (scx, vcx, frx, lbx... did I forget any?), because these files contain their object (or P-code) within their own Object fields. Only the textfile source (prg and any of the ?pr files - mpr, qpr etc) have this duality, that they are compiled into separate files when you run them from the IDE, and compiled into the pjx when you build a project.
>

I found out about about the second copy of the compiled code a while ago, but I always assumed (incorrectly) that when I recompiled all files it recompiled both copies. I also naively thought it recompiled both copies when I edited the PRG, but it only recompiles the FXP. The weird part is that having separate copies in the PJX and FXP didn't cause many problems in VFP 6 but has this major glitch with includes with VFP7 - VFP9. (Granted there were times when I inexplicably got odd messages about the source code not matching, but deleting the FRX to force a recompile always fixed that.)

>Now what's up with your include files, I have no clue. I've seen my share of weird behaviors there, and one thing I know that helps is to have the include directory in the Set("Path").

The folder is in VFP's Set("Path") and it still doesn't work with or without the path part of the Include filename. I suspect the way PRGs get compiled when building and when saving changes is somehow different and the path and current folder are being used for the latter, but not the former.

...Jim
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform