Use Of Online Albums For Collections

I skimmed the list and I also included a field to enter the year of the catalog price and location code (album, page number in some cases).

In my opinion the large number of fields is overkill. The best database table design is when there is nothing left to take away, not when there is nothing left to add. Consider the poor son-of-a-gun (you) who has enter all this data!

The core or main table should not be more than 20 fields. Since it is a relational DB, you can always add additional tables over time. I am unsure what 'drop down' has to do with the database design, a drop down component is an interface element.

You will also need to consider 'data types' when you design the tables; like most things in life there are trade offs with each decision. Unlike spreadsheets, database maintain rigid adherence when entering data; if the DB expects a date then you cannot enter a ???? for the year (if it is unknown). You can establish a value field as a number of numeric data types including specific types like 'currency'. Read up on each data type and understand the pros and cons for the type, do not blindly choose them.

I would start with the establishing the core table and perhaps 2-3 additional tables. I would populate it with a few hundred stamps and then move on to the interface (data entry forms and reports). Make the implementation decisions (platform and tools) and develop your first data entry form and a few simple reports (which would be based upon queries in the database).

When you get to this point, you will have learned a number of things which will facilitate adding additional tables and making your forms and reports more powerful. The last thing you want to do is enter lots of stamp data and then realize you need to make foundational changes to the way you designed the database tables.

A simpler 'main' table with multiple related tables allows for better performance and much more flexibility. For example, rather than having an image field (and I do not recommend storing images in the database but rather just storing file paths to the image file) I typically use a separate 'link' table. The 'link' table supports either absolute or relative links. If you decide to add another image field (perhaps for the stamp back, covers, etc.) or if you want to add a link that returns all ebay 'sold' values; you simply add another field to the 'links' table.
Don

Thank you angore and 51studerbaker, great advice will split the table as suggested thank you, I wanted to put all the fields in that I could use sso as not to add to many in the future, your suggestion on a links table is great thank you

ikeypikey im using libreoffice Base wich is an offshoot of open office.

I enjoy stamp collecting, astronomy and fiddling with computers so if I can combine them all three times the fun,
so I collect Astronomy as a topic, and now do my own album pages and starting my own invetory program. so all the more fun for me