Hi Dejan

>Thanks for looking into this.
>First i guess i can not allow to have NOT parametarised remote view because that's what i was testing. My remote view TEST is not parameterised and i was thinking if i want to see changes to PK value i need to issue REQUERY().
>So if i have table in Oracle with tens of thousands of records when i add new record and issue REQUERY() it will take some time. Right?

Yes - if the view is going to retrieve all records every time. But is that really what you are planning to do? In most Client Server applications you filter queries toprevent that.

>Another thing is if i want to see changes on particular record i need parameterised view. How do i requery() the record i just created? If i create parameter on PK then i don't know that is the new PK value until i REQUERY(). Do you see what i mean?

Yes. As I said, this a major limitation with using Remote Views. But if you are adding records you cannot use the PK as a parameter anyway (whether you use views or not). Probably the best thing to do is to have a second view that uses some combination of columns to display a list of available records (plus their Primary Keys). Then you ReQuery THAT view, find the correct PK and then use that as the parameter when you ReQuery the main view.

Sounds kind of Kludgy I know, but this is what you have to do when the PK is generated by the back end, and you cannot use a stored procedure to handle your updates (which, since you are using remote views, you cannot do).