[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

Re: SQC (Include) files



Hi to all

As far as I know there is no limitation of the include files you can use
(except if there is a limitation of lines in an SQR), just remember that
the include files are appended in execution time to make one big work file.

Just a note, try to use short names in your sqc's to avoid platform
problems and write them in lower case (the same reason).

I've been working with SQR for about 2 years and this is a problem I've
found in platform test

Make sure to include -i  flag with the directory(s) where your SQC's
resides.  Also it doesn't matter if one sqc calls another and so on

Hope this helps and again, sorry about mi english  :o)


Arturo Vega
PeopleSoft Consultant
Mexico City




I have an SQC that only consists of these lines:
        #Include 'AGENCY_INFO.SQC'          ! get buying agency name and
address.
        #Include 'AGENCY_CONTACT_INFO.SQC'  ! get agency contact name and
access
        #Include 'AE_PLANNER_INFO.SQC'      ! get acct exec and planner
names

My question is... what good is it??? It doesn't seem to add much to the
world.... except allowing the programmer to just write #include summary.sqc
instead of including the sqcs above?

I tried only putting this SQC in my working directory and it complains that
it can't find the other ones. Which means, IMHO, that this SQC doesn't
store
the code of the ones it calls.....

So why would you bother writing an SQC that just calls other SQCs and does
nothing itself????

Also, if we usually use most of the code from each of the little SQCs,
should we combine them all into one big file (not really all that big --
about 15 procedures) and just call the big file all the time?

What if we only use some of the little SQCs some of the time? Would the big
file approach be detrimental?
:) Kristin