>Is there anyway to prevent ".null." from populating a field when an outer join is done and no match is found in the child table? I already have SET NULL OFF.

Hi Michael,

I wrote a little utility, called denull.prg, to deal with this problem after the fact, by removing all nulls from the resultant table. This turned out to be a much more efficient solution on large jobs than complicating further processing by having to check for these semi-spurious nulls. See the following link to denull.prg: http://www.ideaxchg.com/ix07/vm/_prg/denull.txt

Mike