My guess is that there was a change in the query optimizer.  it's
evaluating all fields in your select/omit list before determining how to
build the query, and it thinks it will run faster by accessing that field
first.

The only thing i could suggest that you might try is build a logical to do
the select/omit to rid your file of those records and run the query over
that LF.

Rick

------original message------
Just upgraded a customer from V4R3 to V4R5. (yes I KNOW they are WAY behind
but they are regulated etc.etc.etc.) We loaded Every Cume and Group. All is
well except:

  A BUNCH of Queries that ran fine in V4R3 fail with CPD4019, "Select or
omit
error..."  The error goes on to tell us that a field used to construct a
result field contains an invalid value. True statement. However that same
record has always existed (migrated data from DEC system) and has always
contained an invalid value. However that particular record should be (and
always has been) omitted by the select criteria higher in the list than the
ones using the result field that can't be built for this record.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.