Hi Michelle,
Yes I believe you can use fglpc. I do not have any examples but here is the format of the fglpc command:
fglpc { [-ansi]
[-a]
[-anyerr]
[-p <pathname>] } <.4gl source code module> ...
The options in this command are defined as follows:
-ansi makes the compiler check all SQL statements for ANSI compliance.
-a makes the compiler check array bounds at runtime. (Use only for debugging, because of its overhead.)
-anyerr makes the runner set the status variable after evaluating expressions (overriding the WHENEVER ERROR statement in the code).
-p stores objects in the directory specified in <pathname>.
You can compile multiple .4go source code module files by including them in the list, or you can use standard UNIX wildcards to specify the .4gl files to compile. If the compilation is successful, the corresponding .4go files appear in the directory. Otherwise, the appropriate .err files are placed in the current directory (or in the directory indicated by the -p argument) and the developer receives a warning on the terminal screen.
To collect all the object modules and concatenate them into a p-code executable file (.4gi), use the UNIX command cat as follows:
cat <file name>.4go> ... <program name>.4gi
HTH mikey2nicey
"Dream, but don't quit your day job."
