Hi Guys,
I'm currently working on a media database used to store information about my music collection. I've prototyped the database in Access and have upsized it to SQL Server. I'm currently in the process of coding Classes for each of the tables in my database. I've already applied the nested class idea to my primary tables Album Disc and Track in that data that is a foreign key from a database prospective is represented by the class module for that table, ie ArtistID is the Artist Class. There is also a relationship between these three primary tables that I would like to represent in a similar fashion. An Album is comprised of 1 to N Discs and a Disc has 1 to N Tracks. So they should defiantly be defined as another set of nested classes. I am struggling a bit with the best way to accomplish this. I would appreciate any thoughts you might have. I would also appreciate any thoughts you might have on my efforts so far. I've included a class called Book which demonstrates the general ideas of my line of thinking.
I'm currently working on a media database used to store information about my music collection. I've prototyped the database in Access and have upsized it to SQL Server. I'm currently in the process of coding Classes for each of the tables in my database. I've already applied the nested class idea to my primary tables Album Disc and Track in that data that is a foreign key from a database prospective is represented by the class module for that table, ie ArtistID is the Artist Class. There is also a relationship between these three primary tables that I would like to represent in a similar fashion. An Album is comprised of 1 to N Discs and a Disc has 1 to N Tracks. So they should defiantly be defined as another set of nested classes. I am struggling a bit with the best way to accomplish this. I would appreciate any thoughts you might have. I would also appreciate any thoughts you might have on my efforts so far. I've included a class called Book which demonstrates the general ideas of my line of thinking.