Perhaps add a third table AuthorizedUsers that allows a many to one
between users and accounts.
You can maintain the one-one relationship between accounts and Users to
represent the primary uber-authorized user.
-Patti
> I've got a db that includes the following tables:
>
> Accounts
> ------------------
> AccountID PK
> Name
> AccountRepID FK
>
>
> Users
> ------------------
> UserID PK
> Name
> Username
> Password
> AccountID FK
> UserType
>
>
> The Users table will be used for logins to the system. In the Users table
> will be
>
> SysAdmins system administrators
> AccountReps account sales representatives
> AccountOwners Account owners
> AccountUsers Acount editors
>
> I have a 1:1 relationship from Accounts to sales reps in the Users. But
> I'd also like a many:1 relationship from Users who either own accounts or
> are editors of those accounts. I can't have both relationships.
>
> How best to approach this?
>
>
>
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
[Donations and Support]
- OT: DB Design - Bad Case of the Mondays Jim McAtee
- Re: OT: DB Design - Bad Case of the Mondays Ben Doom
- Patricia Lee