Separate the price history file from the data file so multiple sets of accounts can use common history
If the price history were stored seperately to the company accounts data it would ensure integrity of price history accross different entities (ie all your entities are using the same price for a security on any given date). This wouls also mean that prices only need to be updated once (instead of once per data file). In addition the structure required for the price history databse would be far more simple, potentially allowing direct enty into the database from external programs (eg to populate price history).
3
votes
Steve
shared this idea