Originally Posted by
recyan
In addition to June's suggestions, a few thoughts :
CUSTOMERS
One CUSTOMER can have One or Many SITES.
One SITE can have One or Many TANKS.
One Customer's Site today may become another Customer's site tomorrow.
________________________________
tblCustomers
CustomerID - PK
FirstName
LastName
DateOfRegistration
The need for this table tblSites is based on the assumption : One Customer's Site today may become another Customer's site tomorrow.
Assuming, a SITE can be identified by [xCoord] and [yCoord].
tblSites
SiteID - PK
[xCoord]
[yCoord]
tblCustomersSites
CustomersSitesID - PK
CustomerID - FK
SiteID - FK
DateOfSiteRegistration
tblTanks
TankID - PK
TankName
DateOfTankRegistration
SiteID - FK
tblMaintenance
MaintenanceID - PK
TankID - FK
MaintDate
MaintTime
TankLevel
Alarm
Note : Pardon my habit of ignoring csv, current existing scenario, etc, when it comes to design.
Thanks