>>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
Hi Mike,

Nice and simple program, but few observations:

1) Use Command isn't wrapped in some other utility program, so it may throws an error in multi-user environment.

2) Since the query resulting table is already opened exclusively, why not execute this denull program as the last step in Query? Of course, it could be controlled by some Query flags, which defaulted to execution. In this case you would save open table and checking procedure...

HTH