Hi Jeff ---

I think I would disconnect the master project data from direct interaction with the remote data and views. Try making the master project data an array that is requeried fresh when appropriate. I know you'll have to use something other than a grid for the master list, then, but if you adjudicate all of the selection of projects from the array list and stop trying to interact with the master table, you're problems will go away. After all, the master list is not going to be changed, right? Only the subscription list.

>I am using remote views and optimistic table buffering ( I am allowing the users to add/edit/delete multiple child records during an editing session on the parent before commiting the changes). On one form there are two grids, one displaying the names of projects that the parent is subscribed to (this is from a view with optimistic table buffering) and the other is a sql statement that gets all names from a master project list but excludes those found in a select from the subscribed view. I do this to remove items from the second grid when they appear in the first. This works fine with table buffering set to optimistic row but the table buffering causes it to always select all records that have not been committed to the project subscription table and ignore those in the table buffer. I can browse the view and see the uncommited records but the sql statement seems to be ignoring them. Is this akin to the situation where sql refuses to query a cursor file? Does anyone have a
>workaround short of creating a temp file?