Soldato
you probably need to produce a good deal of technical documentation as well, which would usually include a section on technology choice - why you chose desktop vs. web, Java vs. C#, MySQL vs. Oracle, etc. For a final year project I'd also expect you to produce a proper specification and design before you start, which means at the very simplest a list of features that you're going to include, with details on what they are, why they're included, and how they'll work.
This is important.
I wrote an Android app for my final project. It may be different for you but my code was essentially worthless. None of the final mark for the project was from the code. I had to include it all as an appendix though and give a demonstration of my app. I knew from the start that there were 0 marks to be awarded for the actual code but i still got carried away and spent far too much time on it and not enough on the important stuff: the discussion of the choices you made and the analysis of the results.
With this in mind, I would use Access or whatever else you are familiar with for your database. Use whatever is quickest and easiest, there's no need for something that will cope with millions of rows of data and multiple simultaneous connections or anything fancy. Get it done quickly and write as much as you can about what you found out!
(also, it's ok to change your mind about what technologies you use at this stage - a proper software spec shouldnt define programming languages anyway)