Is this design correct?

[jim.thornton]

I am creating a database IN ACCESS 2016 that I can use for organization and display of financial data. Here is what I'm trying to do:
HOUSEHOLD: Each household can hold MANY MEMBERS (spouse/spouse) & MANY STRATEGIES
MEMBERS: Members can only be assigned to ONE HOUSEHOLD. Members can be assigned to MANY STRATEGIES. Members can be assigned to MANY INSURANCE policies and MEMBERS can be assigned to MANY ASSETS.
STRATEGY: STRATEGIES can only be assigned to ONE HOUSEHOLD but there can be MANY STRATEGIES per HOUSEHOLD. MEMBERS can have MANY STRATEGIES. STRATEGIES can be assigned to MANY MEMBERS.
ASSETS: Assets can be assigned to MANY MEMBERS. Assets can only be assigned to ONE STRATEGY.
INSURANCE: INSURANCE can be assigned to MANY MEMBERS, but can only be assigned to ONE STRATEGY. INSURANCE that has a positive CashValue will be listed as an ASSET, but INSURANCE a $0 CashValue is NOT an ASSET.
Have I created these relationships correctly? Would the STRATEGIES table be acting as the junction table to provide the many-to-many relationships for the ASSETS, INSURANCE?


would the HOUSEHOLD table be acting as the junction table to allow MULTIPLE STRATEGIES per MEMBER?
Could someone please help me plan this out?

[ranman256]

I would put ID on the FK ID fields,like:

tHouseholdMembers.HouseHoldID
TAssets.StrategyID

to see instantly what that field is.

[Bob Fitz]

I would also give more meaningful names to all the primary keys. AssetsID, HouseholdsID etc etc