Excel-to-Access Compatibility Issue confirmed

My first deduction was right. The excel worksheet cannot be implementated into Access software properly. The Macro buttons do not show up, neither do any of the autoshapes I assigned them to. The only thing that appears is the writing that I put inside the worksheet without a shape. I cannot implement my system into Access because I would lose many features, Macros and the User-Friendly image I outlined it would have.
This presents a huge problem with the query making and report creation of the system which I outlined in the Specification. Unless I can get the system to work properly in Access (which is highly unlikely) or I can find a way to create queries using the Excel software, the system will not do 15% of what I said it would.
I guess this sacrifice is neccessary. I only lose a small proportion compared to if I just implement it into Access.

Creating an "Exit Program" Macro?

I'm currently trying to brainstorm ideas of creating a macro which exits the systme when instructed. It seems kind of impossible unless you code the whole thing yourself which is like a mega task as I have limited knowledge of coding (HTML). You can't record the macro to exit the system cause you close it and therefore it stops recording. I need to figure out some other ways of doing this.

Possible Programming Clashes

I'm starting to think the Implementation of the Excel Workbook to the Access Workbook is going to be impossible.
See, I'm in two problems. One is that I have discovered that Excel 2007 has the tools for data encryption. Seeing as I thought Access was the only program which could do this, I documented that I would use access for the task. If I were to encrypt the database in excel then emulate it into Access, I can only imagine that many errors would start occuring making it unusable. This is only Theory and yet to be tested.
Another problem is the problem of the Macros. I think switching programs will mess up the coding and screw around with the macros, Layout and perhaps the Condtional Formating (if I end up using it). If it does end up messing around with the macros, I will be in serious problems and might have to do a complete system overhaul to make it compatible.
I will have to test this at the later stages of the Database creation.

Macro Development

So for our IT project, we're on the stage of Implementation. We have to create this system for a business to use and cause I said it has to be user friendly, I was trying to make it that.
Today I started with the Main Menu in Excel 2007. It's a little hard to get to grips with the whole Macro function but now it's pretty easy. I was thinking of a way to get buttons on the excel worksheet (which I named Main Menu) and get them to link to each sheet. I found out (using a little research on google) it could be done using the Record Macro and then Assigning the designed macro to a shape (such as a autoshape rectangle). Although setting up and naming the macro was very daunting at first, it became more easier and now works perfectely.. The only problem is having to save the workbook as a Macro-enabled workbook. Having to use a whole new extension for it to continue working -.-
I now have to create and figure out how to make a Save & Exit Button. Also, I need to find a Office 2007 CD . Can't keep doing all the work at college.