- Joined
- May 10, 2011
- Posts
- 2,048
- Location
- Australia
- Avatar Name
- Shadowsniper Viper Viperstrike
Hi All,
I have created a new thread here to discuss the development of a database I am now writing to contain all elements of the manufacturing process from resources required, blueprints required, subcomponents required and ultimately the end product produced.
It not only has the above, but will have all break even prices verse market markup prices - initially based on the weekly markup values but hopefully later based on the daily markup values if every MA produces a feed for this data. ie. It will be ready to accept such a feed or lookup from their site.
One of the things with databases is that you can auto create table entries into the database for each item.
For example, it may have a main table with many nested tables for each item.
This can get confusing for most so I will try to compile as much info as possible into a single table.
For example, the resources table will have fields such as Resource ID, Record Update Date, Resource Name, Resource Value, Market Markup, Market Markup Trend and so on and so on, but then it would link normally to another table to hold information such as "Blueprints this resource is used in".
What I intend to do is try and put those other tables into the first, so you can more easily manage the database once it is released, instead of creating a thousand entries with a couple of thousand other tables that belong to the main one.
Of course there will be seperate tables in the database for various things such as:
Resources Main Table
Items Main Table
Manufacturing Blueprints Main Table
and so on.
So I will try to keep this database as "simple & compiled" as possible, however as flexible as possible.
I will create forms for entry of data with pull down lists (dropboxes) and YES/NO functionality, most of the data can be entered via clicks but some needs to be updated via data entry such as general notes, refining notes, manufacturing notes that you wish to include for your own reference and data such as the markup data and trend data each week (Although I will do that each week to start with)
Anyhow, I will post a screenshot soon of the entry fields in the CalypsoResourcesMain table.
I am creating tables based on each planet (Calypso initially) as each planet has its own BPs and market information to work with. Calypso will be done first, later in the future we can look at adding other planets.
What I am looking for is fields that may be missing from the design and would like feedback on data fields that may be missing from the table design.
On a final note, this database is being designed in OpenOffice.org BASE, so yes it is free;
As will be the database to all once completed to a satisfactory standard.
Thanks and cheers,
Viper
I have created a new thread here to discuss the development of a database I am now writing to contain all elements of the manufacturing process from resources required, blueprints required, subcomponents required and ultimately the end product produced.
It not only has the above, but will have all break even prices verse market markup prices - initially based on the weekly markup values but hopefully later based on the daily markup values if every MA produces a feed for this data. ie. It will be ready to accept such a feed or lookup from their site.
One of the things with databases is that you can auto create table entries into the database for each item.
For example, it may have a main table with many nested tables for each item.
This can get confusing for most so I will try to compile as much info as possible into a single table.
For example, the resources table will have fields such as Resource ID, Record Update Date, Resource Name, Resource Value, Market Markup, Market Markup Trend and so on and so on, but then it would link normally to another table to hold information such as "Blueprints this resource is used in".
What I intend to do is try and put those other tables into the first, so you can more easily manage the database once it is released, instead of creating a thousand entries with a couple of thousand other tables that belong to the main one.
Of course there will be seperate tables in the database for various things such as:
Resources Main Table
Items Main Table
Manufacturing Blueprints Main Table
and so on.
So I will try to keep this database as "simple & compiled" as possible, however as flexible as possible.
I will create forms for entry of data with pull down lists (dropboxes) and YES/NO functionality, most of the data can be entered via clicks but some needs to be updated via data entry such as general notes, refining notes, manufacturing notes that you wish to include for your own reference and data such as the markup data and trend data each week (Although I will do that each week to start with)
Anyhow, I will post a screenshot soon of the entry fields in the CalypsoResourcesMain table.
I am creating tables based on each planet (Calypso initially) as each planet has its own BPs and market information to work with. Calypso will be done first, later in the future we can look at adding other planets.
What I am looking for is fields that may be missing from the design and would like feedback on data fields that may be missing from the table design.
On a final note, this database is being designed in OpenOffice.org BASE, so yes it is free;
As will be the database to all once completed to a satisfactory standard.
Thanks and cheers,
Viper
Last edited:
.
