>Does anyone know how I can stop Program Generator from deleting all the
>extra globals files that I add to my project's globals group in the Project
>Manager in the FB^3 Editor, each time I edit the project in Program
>Generator ??


Yes. Move the global files down to the area of your filters or your includes.


>(In an effort to make my code more modular, and easier to debug I've moved
>those globals & constants that are include specific into their own glbl
>file(s), so I can just add them to other projects later on, without having
>to manually cut/copy & paste.)


You can group the globals in the file that requires them by using the 
BEGIN GLOBALS and END GLOBALS statements. That way, your globals move 
right along with your file.


>And my recent post about the compiler error:
>
>Error: Internal critical error: PushLevel went Negative! in file
>ladder.¼:FILE.INCL at line 686 in CLOSEFILE **def LONGBLOCKFILL(gSMGblk&,
>_SharedModuleRecSz, _nil)
>
>Error: Missing End ')' Fix it... in file ladder.¼:FILE.INCL at line 686 in
>CLOSEFILE *def LONGBLOCKFILL(gSMGblk&, *_SharedModuleRecSz, _nil))
>
>I had rebuilt my globals as I've described above, and had put the globals
>into their own group in the Project Manager after the std Program Generator
>groups of files, and I had forgotten to BEGIN GLOBALS/END GLOBALS each of
>the GLBL files. PG's std files have a END GLOBALS statement, and that caused
>the compiler not to see my globals declarations, because my globals group
>was after PG's standard groups.


There is currently no way to do what you require. It's one of the 
faults of an old, patched front end. We hope to correct this in the 
future.



Best,

-STAZ  ~)~

800.348.2623 Orders  http://www.stazsoftware.com
228.255.7086 FAX     mailto:staz@...