[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
[sqr-users] Re: Calling multiple files & creating single output file
- Subject: [sqr-users] Re: Calling multiple files & creating single output file
- From: john.tucker@oracle.com
- Date: Wed, 19 Apr 2006 12:00:13 +0000 (GMT)
- Delivery-date: Wed, 19 Apr 2006 08:04:17 -0400
- List-id: "This list is for discussion about the SQR database reportinglanguage from Hyperion Solutions." <sqr-users.sqrug.org>
Seeing the comments on #including gave me another idea. You are correct that
you can't #include an SQR, and the Begin-Program/Report block is a part of the
reason why. OK, I don't actually know of any other reasons, but I assume there
probably are some.
What you could do is change the "secondary" SQRs into SQCs and then #include
the SQCs. Given a main SQR called main.sqr and an SQR you'd like to #include
called second.sqr, here's what I'm thinking:
1) open second.sqr, rename the Begin-Program/Begin-Report block to
Second-Program (or whatever)
2) save it as second.sqc
3) create a new second.sqr that basically consists of four lines of code:
Begin-Program
Do Second-Program
End-Program
#include second.sqc
That would allow you to #include second.sqc in main.sqr and still use it as a
standalone. There may be a bit of additional work to do if you have procedures
that you only want to run if the program's being run as a standalone, but there
are simple ways to take care of that in most cases.
-John Tucker
_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users