|
Ok, so I'm pouring the result of a Left Outer Join into a PF (to be read
by a program that uses Native RLA), and one of the fields "of interest"
is nulled out in several records (as is normal with a Left Outer Join).
If I simply pour it into a file that doesn't allow nulls, it complains
that I'm trying to put null values into fields that don't allow them.
If I change the file I'm pouring my result into, so that it accepts
nulls in the field in question, it works fine, but with an ALWNULL field
as one of the keys, I'm not so sure this thing is very RLA-friendly.list
Is there a way that I can change either my query or my PF, so that the
nulls turn into something else before they get to the PF?
--
James H. H. Lampert
Touchtone Corporation
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.