RE: SQL Optimizer and LF with *OMIT fields

First off, thanks to everyone who responded. The programmer working on 
this did discover the reason for a record not being included in the 
processing, and that was due to circumstances that excluded the record 
(which was outside of the SQL selction criteria). In that regard the SQL 
worked as expected.

"I have never seen the SQL ignore select/omit criteria from a LF." 

I guess the idea in question is that when she had the program in debug 
mode and was reviewing the debug messages generated by SQL, under the 
access path recommendations, the messages showed that the query engine 
chose to ignore all existing views/lf's and used its own. That was 
somewhat misleading because there is no indication that the system 
generated query adhered to the select/omit criteria of the logical file 
specified in the SQL select statement. I think that is what mostly led to 
her questioning the integrity of the query engine.

Thanks again for all the input. Next time I encounter a similar issue I'll 
try to remember this and give it a little extra attention during the 
analysis.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the 
intended recipient(s) and may contain confidential and privileged 
information. Any unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please inform the 
sender by reply e-mail and destroy this and all copies of this message.