Hello Aleksey,
I am sorry for such a delay with reply. The mystery has been solved even though I expected FoxPro to act a little bit differently. The problem was that one of the character fields from one of the joined tables was created wrong in case it would be .NULL. NVL() function was used but rather then PAD() the outcome to the maximum length of the field I used I made it "". So the if the first hit was .NULL. the field was created with 0 length and this caused view generated an error(REQUERY returned -1) while requering and the view was empty, not because there were no data but because FoxPro couldn't requery. Frankly, I expected FoxPro give me an error "View definition has been changed" which we use to have before in similar situation with other views. For some reason it didn't do it this time. As soon as I padded the field to the max length, view started working fine.
That's all it was,
I appreciate your help, thanks a lot.
Igor