O$: Null Fields

Christine Penner christine at ingenioussoftware.com
Tue Apr 21 11:23:57 EDT 2009

Hi Everyone,

We are in the process of converting our software to SQL. In the old 
DML code we never had to deal with nulls much. Now I need some advice 
how to deal with them in some specific problems that have come up. We 
decided in most cases we don't want the overhead of always clearing 
nulls after finding data.

When we have one field we are looking at there is no problem. When we 
have more than one it can cause problems. Here is an example. Any 
suggestions would be appreciated.


In this case we compare old and new values to see if anything has 
changed. Typically in this situation everything will be null except 
pNewRow.FF_HIRED. It still fails though because of the nulls. We do 
this type of thing all over the program. It would be good to not have 
to write a pile of code each time checking for nulls.


More information about the omnisdev-en mailing list