Stew,

It sounds like you've set everything up right. Here's how to get more information on what's causing the problem:

1. USE the view in the command window.
2. Go to the record you want to change.
3. Modify it using the REPLACE command (REPLACE myfield WITH 'X')
4. Type ?TABLEUPDATE().
5. Type AERROR(aError)
6. Type DISPLAY MEMORY LIKE aError

You should now see the error returned by the ODBC driver, if any. You may not have rights to modify the underlying table or there may be some other configuration issue. It sounds like you've set up the view correctly.

>Regarding Updateable Views to a Remote Btrieve Table using ODBC....
>
>I have a connection and a view setup. I have the project opened in project manager. I highlight the view and press browse and I can see all of the data. I make a change to a single field in a single record, move off the row and the data remains on screen. I close the browse and re-open it and I see my changed data.
>
>If I close the project and re-open it, my changed data has reverted to its original form.
>
>Why isn't my data written?
>
>From what I gather, I think my change only went into the view and NOT to the underlying Btrieve Table. I want this data written to the BTRIEVE table (later on.. I'll do this with code).
>
>In the view designer, in the update criteria tab, I have the send SQL update checked on, one field checked as the key, and my editable field checked on in the pencil column to indicate its a writeable field.
>
>I have experimented with tableupdate too without any luck.
>
>Also to note... I tried updating some other fields in the remote btrieve table from the view other than the one I'm really focusing on. I can update these other fields. The one that I want to update I can't. This happens to be a field I added to the BTRIEVE table using the tools provided by Pervasive and Platinum (its a table in a Platinum Acctg System).
>
>I checked the normal stuff - its in the data dictionary. I'm pointing to the correct set of .ddf files in the correct directory.
>
>BTW, below is each buffer mode command the VFp reaction I get on my system.
>
>cursorsetprop("buffering",1)
>cursorsetprop("buffering",2)
>cursorsetprop("buffering",4)
>
>^^ All three of these attempted settings result in a VFP error dialog stating:
>Views require either DB_BUFOPTROW or DB_BUFOPTTABLE
>
>cursorsetprop("buffering",3)
>
>^^ No error when set, but inside the view I get 'update conflict' (must use table revert to get out)
>
>cursorsetprop("buffering",5)
>
>^^ No error when set or inside the view but no update occurs. (useless)
>
>Can someone please steer me in the right direction?
>
>TIA,
>
>Stew