On 5 Jul 98, at 13:40, Bernd Corsten-Weseloh wrote:

> even if you find an easy way to locate and compile your PH files (or most
> of them) automatically, you may want to bear in mind, that only screens
> compile without problems in the same QDESIGN session. QUIZ and QTP tend to
> include many "SET" options, that stay valid and are carried on into the
> compile of the next source. If you don`t restart QUIZ/QTP before any 'use
> source' command, you are likely to get some very surprising results...
>

There are many ways around the problem of inherited SET statements,
but the cleanest that I have found is to adopt the practice of adding the
statement "SET DEFAULT"  followed by "SET NOLIST" to the end of every
source code file.

I use conditional compiler flags in many of my Powerhouse source files to
generate audience specific variants of the same basic program, be it a
screen or a report.  To handle the special requirements of mass
recompilations involving compiler flags (like I had to do on Saturday last) I
create mini "source" files for these that use the same nomenclature as a
regular source file (QXyyyyyS) but which contain a call to the necessary
PH compiler component along with the required flags, source code file,
and a final "EXIT" statement to return to the main component (QDESIGN,
QUIZ or QTP) upon completion.

Architect then has these files placed in its database and it feeds them to
the application compile command just as if they were regular source files.
 Works great.

The main difficulty that I find with manually constructed compiler job files
is that they will always end up out of date and the work necessary to vet
them when needed sometimes exceeds that required to build one from
scratch.

Regards,
Jim

---
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
mailto:[log in to unmask]  Canada L8E 3C3