Jim: What is strange is that the table data is fine -- nulls are empty nulls. On the form, the located fields are empty and they LOOK empty. It is only when I set a form variable to the value of the field that the VARIABLE has an $8 in it. That's the weird part. So it has to do with how variables are interpreting a null value.
As you suggested, I was thinking of adding a default value of $0 to the table column but they really wanted to distinguish between a null value and a $0 entered value. And since there isn't a problem with the table data, only its visual representation on the form, I hesitate making a table definition change.... Since I found a workaround I think I'll skip modifying the table structure. Karen In a message dated 10/11/2011 12:19:29 PM Central Daylight Time, [email protected] writes: > My guess is that the $8 represents the "NULL" internal value actually > used to represent a NULL value. Way back when I was updating older to newer > versions of RBase > I had a problem with NULL values. > > In my opinion I would alter the Table Definition to add DEFAULT values to > those fields of $0.00. Quite possibly I would also make the NOT NULL. sit > that cikuns would always require a value. > Also a RULE for each column requiring say a value of $0.00 or greater be > required. >
