Yes, you can buffer your view, in fact, you must buffer a view. Tableupdate will send updates back to your source table (provided you've defined the view properly). You DO NO want to open the source table yourself. Let the view do that for you. If there's some reason you must open the source table, you'll want to have buffering off for that table if you can. Otherwise, you'll have to Tableupdate() the source table too.

>Sounds like a good work around...
>
>What if I want to use the grid for data entry, can I buffer it? Will the actual table be updated when I issue tableupdate()?
>
>That would mean we will have to create a view for all the grids in our system I guess.
>
>Right?
>
>>Frankly, I've often had this problem trying to use the LinkMaster and RelationalExpr properties and never could figure out why. I don't even try anymore. I just use a parameterized view instead.
>>
>>>Hi all...
>>>
>>>I am having a problem with grids I have never had before and I can't seem to find a solution.
>>>
>>>The grid behaves as if it's doing a seek in the child table based on the parent field. I see all the records of the table the grid is bound to, but when the parent moves, the grid moves to the right record *without filtering out* the records that do not match the key.
>>>
>>>What am I doing wrong?
>>>
>>>Thanks in advance...