Ahhhh, so I'm not the only one. I'm retreiving data
through the View Desginer. I usually don't use it but
for quick and dirty stuff. I guess when it comes to
nulls on the backend, VFP's View Designer is not quick
and dirty. It just doesn't work with NULLs.

Too bad. I had them install VFP here (they use MS Access)
thinking the programmers would like it. But if they can't
do even simple updates, guess VFP is useless for them.

One thing is nice. VFP displays .NULL. instead of a
.BLANK. as MS Access does. It is sure nice to know when
something is .NULL. and not just .BLANK.

SQL passthrough is too awarkward for on-the-fly updates.
That's why there are browse type windows. But I wouldn't
use anything but sql passthrough when I program.

Now if we could just update NULLs in browse windows.
Oh well, back to MS Access.

Thanks for your reply.

> How are you retreiving the back-end data?
> With a updatable Remote View? I have had trouble
> with RVs on the backend. They do not seem to
> pass .NULL. and they pad character fields with
> trailing blanks. Therefore a varchar field becomes
> the maximum field width even with only one character.
>
> Try using SQL passthrough, that works the way its
> supposed to. I have gotten away from using RVs with
> updates.