Re: debug sqr error?

[Allen Cunningham <allen.cunningham@SONOMA.EDU>]

Hi Mark - Thanks for the input, but I ended up finding the problem. Here is
a post-mortem of the problem:
Somehow a single control char got introduced into the sqr text file, at the
very bottom past the last '#include'. It showed up like a small box in a
text editor. The sqr ran fine on the client, becuase Win NT doesn't care
about such things, but on the unix server it did care, and generated the
error of finding a command outside of a begin-end block.

ac

-----Original Message-----
From: Discussion of SQR, Brio Technology's database reporting language
[mailto:SQR-USERS@list.iex.net]On Behalf Of Risman, Mark
Sent: Thursday, October 04, 2001 8:15 AM
To: SQR-USERS@list.iex.net
Subject: Re: debug sqr error?


Allen,

Check to see that this #include line is in the right spot.  I believe that
whatever is inside the included file will
show up in the calling SQR, exactly in place of the "#include" statement;
the compiler replaced the #include statement
with the file and then compiles the whole thing.  If you do something like
this, for example:

BEGIN-PROCEDURE
.
.
.
#include 'xyz.sqc'
.
.
.
END-PROCEDURE


and your sqc has:

BEGIN-PROCEDURE
.
.
.
END-PROCEDURE



then the final version would look like this

BEGIN-PROCEDURE
.
.
.
BEGIN-PROCEDURE
.
.
.
END-PROCEDURE
.
.
.
END-PROCEDURE

and the compiler would get confused and you'll get an error kind of like the
one you saw.

hope this helps,
- Mark


-----Original Message-----
From: Allen Cunningham [mailto:allen.cunningham@SONOMA.EDU]
Sent: Tuesday, October 02, 2001 6:46 PM
To: SQR-USERS@list.iex.net
Subject: Re: debug sqr error?


Actually the error is occuring on the next to last line of the sqr, just
before the last comment line, see below. Also, this sqr runs fine on the
client, but bombs on the server.

#Include 'songetdb.sqc'   !Custom - Get Database Name (THIS IS LINE 1612)
!---------------------------- End of Program --------------------------

Also, so anytime I see an error on a line number, it will be pointing to the
sqr itself? Not to included sqc code that has been brought in to the sqr?

ac


-----Original Message-----
From: Discussion of SQR, Brio Technology's database reporting language
[mailto:SQR-USERS@list.iex.net]On Behalf Of laura lopez
Sent: Tuesday, October 02, 2001 3:31 PM
To: SQR-USERS@list.iex.net
Subject: Re: debug sqr error?


Allen, when the error is in the SQC, it actually tells you.  I'd tell you:
'error in the include file...  line ....'

The error you're getting is because you have a procedure that does not begin
or end with the keywords: "BEGIN-procedure ..." or "end-procedure ..."
check your code on that line (1612) and make sure you do have those keywords
if it is the beginning or end of a procedure.

Hope that helps!

Good luck!

Laura.

> -----Original Message-----
> From: Allen Cunningham [SMTP:allen.cunningham@SONOMA.EDU]
> Sent: Tuesday, October 02, 2001 3:11 PM
> To:   SQR-USERS@list.iex.net
> Subject:      debug sqr error?
>
> sqr version 4.3.4
> database Oracle
>
> I get the following error when running sqr:
> Error on line 1612:
>    (SQR 4702) Line found outside paragraph.
>
> Since SQC's are included how can I know if this is the correct line where
> the error is occuring??

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.