>>>Peter,
>>>
>>>What is the problem with;
>>>
>>> Cursorsetprop("BUFFERING",3,"Allproperties")
>>> Requery("allproperties")
>>> CursorSetProp("BUFFERING",5,"Allproperties")
>>
>>Jim,
>>
>>Thank you for your speedy reply. The problem is not Allproperties but SelectedProperties. Obviously I would like some sort of user confirmation before writing the stuff in SelectedProperties to the basetable , but at the same time, I would also like to remove the items that are already in the SelectedProperties view from the Allproperties View as soon as the user has selected an item in the Allproperties View. That´s the WHERE NOT EXISTS part of the query.
>>
>>It seems like VFP does not even look at the stuff in SelectedProperties unless you perform a tableupdate(), which is exactly what I don´t want to do at this time.
>>
>>The whole thing is a mover class with 2 List boxes and an Add & Remove button.
>>If you´re interested I can send it to you.
>>
>>I hope this is clear enough and I´d be much obliged for further input!
>>
>>Best regards
>>
>>Peter
>
>Peter, AFAIK a view looks at the original data of a table/view and does NOT included buffered data. If your views are small enough, could you create a cursor or temporary table, add the items you wish to use in your your View and then run the view off of the new cursor instead of the View? This should be invisible to the user if there are less than 100 items.
>
>I hope this is clear....
>
>Barbara

Barbara,

Yep! It´s clear enough. Thank you for your interest in this matter. I have in fact programmed a version that does work this way, I just wanted to know if there was a way around this (somewhat annoying) behaviour in views.

Regards

Peter