This makes no sense Gene. I do this all the time and it has always worked. I noticed in your response you typed CTRL-O (the letter O) It should be CTRL-0 (the number 0). I am currently using VFP 6.

I just created a test table in SQL Server with two char fields, (and a primary key) added a record with data through a remote view, updated it, closed it, opened it, replaced the data with CTRL-0 (NULL) and it worked exactly as it should. (The fields are also marked as accepting NULLS)

So, something else must be different if your results don't match. What can it be?


>I tried the CTRL-O and it didn't work. Does anyone have any other ideas? For some reason MS Access does it automatically whereas VFP can't seem to put a null into a field on a backend.
>
>>>Visual FoxPro 5.0
>>>On the backend, a numeric field that allows NULLS.
>>>
>>>When I pulled up the table by a remote view (in a browse
>>>window), the field had a value in it. I wanted to change
>>>that value (let us say 76) to a NULL.
>>>
>>>How do I do it?
>>> I typed NULL.
>>> I type .NULL.
>>>
>>>It kept changing itself to the zero (o) which is incorrect.
>>>I don't want a zero, I want it to be NULL.
>>>
>>>I went to the Visual FoxPro menu item:
>>> Table
>>> Replace Field
>>> With (command button)
>>> Logical Dropdown and chose NULL.
>>>
>>>Once again it changed itself to the zero (o) which is incorrect.
>>>I don't want a zero, I want it to be NULL.
>>>
>>>So how do I put a NULL in the field from VFP.
>>>Yes, I double checked and the field on the backend
>>>allows NULLs.
>>>
>>>Thanks
>>
>>
>>Type CTRL-0 in the field. That should change the value to a NULL (CTRL-ZERO)