RE: SQL Problem

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

Mark,

Warning, I may be out in left field because I don't really use embedded SQL.
Is it possible that the indicator variable that it is complaining about is
the null/not null flag(s)?  Since the fields from the secondary record don't
have a value in these cases they may be coming across as null's and you
haven't provided a place to put the null's.  Having said that, and on the
off chance that it is on the right track, I don't know enough to tell you
how to fix it but perhaps this will trigger someone else who does know.
Either you have to provide a place to put the null indicators or you need to
force the secondary file fields to some default value if no matching record
is found.

HTH

Scott Mildenberger

> -----Original Message-----
> From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com]
> Sent: Thursday, September 13, 2001 2:40 PM
> To: rpg400-l@midrange.com
> Subject: SQL Problem
>
>
>
> If anyone has any information on why I'm receiving a sqlcod of -305
> (Indicator variable required) on a LEFT OUTER JOIN when there are
> non-matching primary records with the secondary record, I'd appreciate
> being left in on it. There aren't any indicator variables in
> the table. I
> didn't even think you could put indicator variables in a PF.
> At least using
> DDS.
>
> Thanks,
>
> Mark
>