Gene;
I'm glad you got it worked out. I am using the Codebook framework with Remote views. I do use some SQL passthrough but probably not more than 10% of the time. I use business objects with every table that can be updated. Since they are all connected through object relationships a call to an IsChanged() function lets me know if any data in any view has changed.

The updates are handled by a relatively simple tableupdate and the view designer allows you to set the updateable fields. This is really useful with views that join to code tables for the descriptions but those fields are not marked as updateable.

I also haven't found SQL passthrough to be any faster. It probably is but I am quite content with the speed of ODBC. I am always amazed at how fast data can be retrieved (Sometimes!)


>Bob,
>
>Thanks!!! ... there sure was a difference between CTRL-o (leeter O) and
>CTRL-0 (zero). Yeah, back to VFP. It is such a joy writing code in
>VFP.
>
>Also, I've noticed that Access doesn't do outer joins (at least I haven't
>found a way) in their query designer like VFP does.
>
>Unfortunately I am using an Oracle backend (instead of MS SQL Server)
>and I guess I jumped too quickly to conclusions that VFP\Oracle aren't
>suited for each other. I have found Oracle (in program code) is basically
>the same as MS SQL Server.
>
>Guess when it doesn't make sense it just doesn't make sense.
>
>Thanks again!!!
>
>>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)