>thanks, Cetin, but the "users" that we are talking about maybe other programmers in our team...

---

That's why I don't work with a team :) Kidding.
Then you should create "view designer proof" views. One way is to change the sql to something that designer would complain it's too complex and wouldn'topen at all :

CREATE SQL VIEW "MYVIEW" ; 
   AS SELECT a.*   ;
   FROM mydata a  ;
   WHERE a.f1 = ?m.V1  ;
     AND a.f2 = ?m.V2  ;
     AND a.f5 = ?m.V5  ;
     AND a.f6 = ?m.V6  ;
     AND a.pk in ;
     (select pk from mydata b where b.f3 = ?m.V3 or b.f4 = ?m.V4)

Only shortcoming is that you cannot set update criteria and other properties visually (nonvisual view). You have to code all of them. That's not a big concern though.
Cetin