It appears that each record refers to one and only one device. If that is the case, there is no need for the join table between stations and devices. A station ID field can link each device to the station where it is installed.
Thank you for your reply.
Each station has multiple devices, one or more servers and each device had a config information. My problem is to link the tables together so that I can call a table to another table.
The diagram I put was without the relationships. That's where I'm stuck.
Get Outlook for iOS<https://aka.ms/o0ukef>
Yes, but the crucial question is this:
What does one record in your Devices table represent?
If it is one type of device where many devices of that type might be placed at any number of stations, you need the join table, but some of the fields that you've placed in devices would then need to be moved to the join table.
If a record in Devices only refers to one specific device, then there is no need for the join table and you can thus remove the StationDevices data model and add an FK field for station ID to Devices.
So which approach to Devices are you employing?
In addition, you need a StationID field so that you can link station records by ID rather than name.
Devices - I need to create a drop down list of the different type of devices. This should include a field to state which devices are active and which are inactive. There should be notes field where we can enter information as to why a device is inactive etc.
You won't be able to solve this problem with a simple drop down list. You'll need a popover with a portal in it.