Looks like a good start. I'd work on using the form wizard and design your forms for the tblDivision and tblPitch. After you get done with this, then design the form for your tblTeams. You'll probably want to utilize 2 comboboxes on this form - 1 based on the tblDivision and the other combobox based on the tblPitch (see some of the combobox examples in the code bank or perhaps read the help on comboboxes.) You can also look at the Northwind database (which comes with MSAccess) and get some good tips there.
I can possibly foresee a tblGames table where you have a TeamID1 and TeamID2 (and possibly the PitchID's) and the dates (or DateID) versus (or in conjunction with) the tblDates table as I'm not quite sure how your tblDates is going to fit into the picture but another upload after you get more developed will help clarify that.
Also, I'm not sure if you plan on tracking when a PitchID gets traded from one team to another but it's something you may or may not want to consider. The way you have it set up now though, you could easily change a PitchID in the tblTeams table for trading purposes. Not quite sure what you mean by a shared Pitch though. You'll need to clarify this more for me to help as I don't have a lot of knowledge on how this works. Maybe the tblGames would work with the PitchID's. Otherwise, if teams share PitchID's, you could either have a PitchID1 and PitchID2, etc in the tblTeams or you could go 1 step further in making another relational table for PitchID's to tblTeams (ie. another relational table (ie. tblTeamPitchers) which has TeamID and PitchID in it.)
Again though, try and develop some more and then upload it as someone like me who isn't experienced with how this all works, I can't really say if it's set up exactly like it's supposed to work. Maybe someone who's more experienced with the concepts of the project can help you more. From a design concept without the background knowledge of the project, it looks like your going in the right direction.
And honestly, I only looked at it quickly. I would need a little more time reading your requirements to give you a more accurate diagnoses if you're on the right track. I apologize but I just can't do that now. Again, maybe someone else here can give you a better diagnoses.
Last edited by pkstormy; 06-20-08 at 21:44.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)