Looks like someone loves to include files ;-)
-----Original Message-----
From: Love, Kristin [mailto:klove@MSA.COM]
Sent: Friday, October 15, 1999 7:49 AM
To: Multiple recipients of list SQR-USERS
Subject: SQC (Include) files
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