[AccessD] Fwd: FW: table design

[David McAfee]

Hmmmm, this is a different way of looking at it

I keep thinking in a many to many situation, but there are a few one to
many situations.

At any point of time you can have:
>
> One phone number attached to one account.
>

1500 phones tied to 6 accounts



One phone number attached to one SIM.
>
At a time,  yes, this is correct. But a sim can be pulled or moved to a
different phone.



More than one SIM in some phones
>
Theoretically yes, but we don't have a need. We are a local company, never
travel out of our country. But I guess having a many to many table
structure would handle that.


Multiple phones per employee
>

Not supposed to. The only time that I have seen this so far is when the
techs leave an old/damaged phone assigned to them. I plan to handle this on
the front end of my app.