Conceptually you populate combo box #1. You then wire up an event to populate combo box #2 upon change in selection of the contents of Combo box #1.  The same logic can then be extended to the third control and so forth.

Obviously your choice of tools bears into how you implement your solution.  Certain vendors provide controls with cascading events designed to handle "related" controls (such as Telerik for example). Heck with the right vendor you could be 100% code free.

Have you tried google for your solution?  (Give up on Bing).

What is it with meteor's and Russia?  They seem to attract the like moths to a the flame.  Didn't they have one earlier which flattened 700 miles of forest in Siberia?  

As an example you could fire up Access and have your project in about 20 minutes.  

You could fire up Visual Studio (Professional Edition) and use the database tools to create an "object" based solution.  It, depending upon the version you own could even create the database in a SQLEXPRESS edition SQL Server for you.  You could then use the various wizards within Visual Studio to create a virtually code free solution to interact with the database you just created.

If you are restricted to tools which are not quite so friendly you can do it "old school".  For example using MySQL you can manually create the database tables.  You could then use the Express editions of .NET (pick your favorite language) and write the code to interface your program to the MySQL database.  This of course would require the most coding on your part as you would likely have to construct SQL expressions to perform your updates.  Of course this is probably the goal of your assignment - to actually learn how to code.

The problems I am seeing, since updating to update #1, all boil down to file locking problems. I get resources are busy or simple "hung" never returning from "auto checkout" events.  Stopping Visual Studio and relaunching the project solves things however it is very annoying.

Since UPDATE 1 I am getting freezes during "performing check-out" operations.  A reboot seems to fixes things for a while however the problem reoccurs.

It seems to be a timeout error.

Is anyone else seeing this? 

I support people living by the results of their own choices.  If we want to start printing "this product will kill you" on all tobacco products that will preclude people from buying them.  I would point out that life causes death after all.  There is nothing we can do about it.

This might be what you are seeing.

System.IO.FileStream fs = System.IO.File.Open("filename", System.IO.FileMode.Append);

is one of the many ways you could do it.

(I have yet to see why I should upgrade to TFS 2012 other than the nice new number)

Under VS 2010, I could right click on the "Team Explorers" tree and select "Find In Source Control" by "status".  In VS 2012 I am limited to changesets, labels, or shelve sets.  I cannot find by status or wildcards like I could under VS 2010.

As I am still pointed to the same TFS server, I would not expect this. If anyone can point to where they moved this feature, please sound off.

If you operate from the view point that "someone has to keep you secure", I disagree with the philosophy.  I have been on the net since 1979, before 2400 baud modems, with zero infections.  No, that is not zero known infections, that is zero infections.  I am the guy you call when all of your Catholic schools computers have been broadcasting porn all summer and you need to open tomorrow.  (A real life scenario which I have helped out at)  

Yes you could write your own program which provides you with these features but why??

My major recommendation:  Given the poor performance of Access, under load, why tempt fate with a cloud based solution?

I am familiar with the basics of database design.  I know when indexes are required, how to tune queries and such. If you are relying upon the "relationship" tool within access to optimize your database you are missing a lot of performance. 

If you are going to be migrating your application into a pure SQL database with an Access front end then get completely out of Access (data wise) and forget the toys.

I have migrated several major customized access database/applications used by several local municipalities with success.

One word of caution:  Watch out for the "Denial of Service" attack that Access will do on your SQL server.  The default login for Access is a user named "Admin".  If you use windows authentication against SQL, it will attempt to authenticate first as "Admin", then using the users credentials.  The combined number of users running your application can form an effective denial of service attack (even though it is unintended).  The only method I found around this was to not use windows authentication against SQL.

It looks like there are several new "toys" in the mix.

Copied to a network location the files are roughly 24 GB in size.  So how did they fit that all on one DVD?  The disc is not blue-ray.  Is this a case of "de-duping"?

Needless to say I was surprised by the results.  The disk does not appear to be damaged in any manner.