>>I have 2.6 tables that I need to be able to place in a tranaction and be able to roll back. You can't rollback a table that is not a member of a database container, but Jim Booth pointed out to me that I could use an Updateable view. What is the procedure for rolling back an updateable view? Here is roughly what I am doing, but it doesn't seem to work:
>>
>>TableA (2.6 table)
>>ViewA (Updateable view made up of fields from TableA)
>>
>>CURSORSETPROP("buffering", 5, "TableA")
>>
>>BEGIN TRANSACTION
>> IF !UpdateTableA()
>> llSuccess = .F.
>> ENDIF
>> IF !UpdateTableB()
>> llSuccess = .F.
>> ENDIF
>> IF !UpdateTableC()
>> llSuccess = .F.
>> ENDIF
>> IF llSuccess = .T.
>> ENDTRANSACTION
>> ELSE
>> ROLLBACK
>> ENDIF
>>
>>********************
>>Method UpdateTableA (UdateTableB and UpdateTableC the same)
>>
>>SELECT ViewA
>>APPEND BLANK
>>REPLACE ViewA.Field1 WITH "Test",
>> ViewA.Field2 WITH "Test2"
>>
>>TABLEUPDATE(0,.T., "TableA")
>Ed, I think you'd better set the view updateable and update it. This would update base tables provided that you set the correct update options.

Cetin

In the Update Criteria Tab, the correct table is selected, I have all of the fields set to updatable, the send SQL Updates box is checked, and the Key and Updatable Fields radio button is selected.
I do this:
SELECT ViewA
APPEND BLANK
REPLACE ViewA.Test WITH "Test"

When I look at TableA, it has not been updated. When I look at ViewA the View displays the added field and entry. But when I click on something in the browse window for ViewA. I get the error "Cannot insert an empty row from a view into its base table". I must be missing something basic here. Have any ideas?

Ed