Disturbing Asset Discovery

Hi,
      We are on BPCS V6.04 with that same version of Asset. I made a copy
of an existing Asset program that has many SQL commands in it. I changed my
primary file to another one.  It compiled fine and ran with no halts. As I
was looking at the data, I found some items that did not update correctly.
I traced it back to a subroutine with an SQL declare followed by the open,
fetch and a bunch of other calculations. When I looked at the asset source,
everything was fine.  When I put it in debug, I entered the SR, but there
was nothing there.
      What had happened was that in the where portion of the declare, I had
a field that was no longer defined.  The only RPG code generated for the
subroutine was BEGSR & ENDSR. No compile error, no run error, no code.  The
scary part is this SR only affected about 1/4 of the items. I could have
very easily looked at some items and thought everything was OK, and put it
into production. Luckily, I'm kind of anal sometimes :)
      Is it normal that SQL statements are not checked for validity? When I
fixed the field name, everything was OK.

<===================================================>

Terri Harteau
****************
"There's no point in being grown up if you can't be childish sometimes."
- Dr. Who
****************