I think your original idea was the correct one. Views can be pretty troubling, here are some things to check:

1. Are you sure you have SendUpdates = .T.
2. Does the view have a primary key it can use to update the base table, and is it set in the view (KeyField = .T.)
3. What kind of error are you getting back from the TABLEUPDATE() with AERROR()?

>I am trying to make an edit screen for a jobs table (an order can have several jobs). In that table there is a field called iLocationID that refers to a location that is needed for that job. Now instead of ID number I am trying to display the actual location name which is stored in another table.
>
>My initial thought to do this was to create a view for that jobs business object that had an inner join with the locations table so it could retieve the location name. I then specified that all the fields in that view (except for the location name) were updateable. I think this caused an error when I tried to save a new record.
>
>My next try was to put two views in that business object. The first one was just a plain old view of the jobs table without the inner join and the second was was the one with the inner join. I was thinking that I could refer to the second table in my grid for display purposes but it would only try to save to the first view in the object. I got some strange results.
>
>I then tried to create two object. One for display purposes and one to save. I think I was getting strange results here too.
>
>This must be a pretty common thing that people do so I am wondering what is the recommended way to do it?
>
>Thank you,
>Erik