>Dear Foxpro'ers,
>
>We decided to use views for all of our forms.
>
>In our security form I use page frames. The first page called " rights per users" I have text fields in which you can put a user. Also I have a grid. In the grid I have a combination of two tables.
>Items table and acces table.
>
>In the user table you will find the user information.
>In the items table you will find all the different modules which can be accessed
>In the access table you can see if a user has access to an Item
>
>I made a view combining the tree tables. I have related the tables like this: User --> Useracces --> Item
>
>But in the grid I will see all the items of all the users when I select one user.
>
>I have tought to make a view only with Useracces and item and then make a relation with a User view.
>
>The second page called " Item acces" I'm looking the other way around. I select an Item and I can see which user has access to it.
>
>So I also made a view combining the tree tables. I have relatet the tables like this: Item --> Useraccess --> User
>
>I suffered with the same problem with the information displayd on the grid.
>
>My questions are:
>
> How can I solve this problem the right way?
> Can you make so many views as you want from on table and use it in a form, or are the limitations?
>
>
>I'm looking forward to your reply
>
>
>Your Faithfully
>
>
>Luco Buhrs
>
>On Koos Veel's account

Number of views is unlimited. However, you should look at this realistically: the main advantage of view is that it's updatable recordset. So, if you want some recordset for viewing purpose only, then using of view ir overhead. In regard to your specific problem: you should use parameterized view (e.g. by ?nUserId) to bring information pertained to one particular user. IOW, your textbox should get UserId value, e.g. in LostFocus event (usually, it's appropriate to have combo and InteractiveChange event here), and this event will fire Requery("view") refreshing view recordset.