Re: SQL null indicators when not all columns are null capable

What does DATFMT() show in PRTSQLINF? How is the variable ReceivedBack declared according to the listing? Does the returned data match the expected format; i.e. the SQL date format? If the LIKE declared variable appears other than as DATE(10), what if the variable is declared instead, explicitly as an alphanumeric with a length of 10 bytes?

Regards, Chuck

Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

I'm working on a program to fetch records from a table where
some of the fields are defined as null and others defined as
not null. I am doing a multiple row fetch and what happens is
the first row returned is fine but every row after that is
shifted four bytes as if there are four bytes missing from the
buffer. I don't think it is a coincidence that there are two
non-null capable fields in the result row and the indicator size
is two bytes for a total of four bytes. I have tried changing the
size of the indicator array but it didn't help. Before the table
was changed to allow nulls this same fetch was returning the
records correctly.

<<SNIP>>

// Format of returned SQL record.
d ResultSet ds Dim(340) Qualified
<<SNIP>>
d ReceivedBack Like(RcvdBack)
<<SNIP>>