If that is the case then it underlines the importance of a "Database Abstraction Layer" where the code does not access any tables but accesses either views or stored procedures. Then those in use do not get altered even when/if the table changes but new ones are created for usage in new places within the code.
yes, you can end up with a lot of similar ones, but, let's face it, the storage for those is minimal and a naming convention deals with managing them.
Agreed!
The logical place to start would be to fix the station alignment. This could fix many problems related to co-ordinates etc, even mining.
If the universe is out of place, then everything else will stop working.
Notice in pic the station hologram compared to the actual station.