< Groan > I was hoping I wouldn't have to do something like that. Thanks, I see what happens.

>I always use an extra field in those cases. Place the current record status in the field (example: 1=new).
>
>>Hi David,
>>
>>Ug. I kept looking at the Numeric type in the help. Thanks.
>>
>>So any ideas how tell if it's 0 for a newly appended blank record? I append a blank a record to a view, then show the user a form to edit it. I need to tell if the user picked 0 or if it is 0 from the append.
>>
>>Here's what wierd. If it's a remote view using ODBC to connect to a VFP table (with that field marked to not allow null's). Append to the view, the field has a 0. Now TableUpdate it, you get an error "Field XXX does not allow NULL's". ???
>>
>>
>>
>>
>>>Uh, guys...
>>>
>>>The help also says this:
>>>
>>>Note that Currency, Integer and Double type expressions are never blank, and ISBLANK( ) always returns false (.F.) for these data types.
>>>
>>>So you are seeing the documented return value for Integer.
>>>
>>>>Whew! I thought I was going nuts ;) Thanks.
>>>>
>>>>Now I need to find a work around.
>>>>
>>>>>I get the same results. Looks like you found a bug, at least according to the help file's definition of how IsBlank() should work.