>I'm attempting to create a complicated view of some M-M relationships. This will be a user form for a security system. The form will contain a pageframe..page 1 is the user information, Page 2 the groups the user belongs to (selected via a mover), and Page 3 the additional rights the user has (set via a grid). My files are layed out like this (I've only included pertinent fields):
>
>Users
>-------------
>pkUsers (primary Key)
>UserId
>
>Groups
>------------
>pkGroups (primary Key)
>
>UserGrp
>-------------
>pkUserGrp (primary key)
>rkUsers (relates to Users.pkUsers)
>rkGroups (relates to Groups.pkGroups)
>
>Items (All possible items that you can assign rights)
>---------------
>pkItems (primary Key)
>
>UserItem
>--------------
>pkUserItem (primary Key)
>rkUsers (relates to User.pkUsers)
>rkItems (relates to Items.pkItems)
>
>So, UserGrp is used to link Users.dbf to Groups.Dbf and UserItem is used to link User.dbf to Items.dbf
>
>This should be setup so that the user will enter a UserId to update and then a parameterized view will be populated. My question is, how do I create the view? I keep getting errors from the view designer that certain key linking fields can't be found. The exact field varies, depending on the order that I add tables to the view designer.

how is your dbc set up? we've done this a few times and haven't found a way to set the relations in the dbc wo/ running into problems w/ them. in the end, we just left the relations out and added them based on which end of the looking glass we were using...