Excel Database Design

Don't let the title throw you off. I'm not looking to create any sort of externally sourced database (E.G. Access), instead I'm looking to store some information directly in Excel in a database-style environment.

I have a time-sheet that I created for work to keep track of my hours and jobs (per company policy). I'm handling it on a weekly basis: Monday - Saturday, and each week is stored as a new tab. I noticed that the size of the file got decently large after a couple months so I went into my code which was stored per worksheet and reduced it to a couple calls from ThisWorkbook vs having each procedure stored within every worksheet (which was created and duplicated every week). Beyond that, every new worksheet has several named ranges which are copied from the previous week. Now I'm up to 20+ tabs which in the grand scheme of things isn't crazy, and to be honest, 2 years from now won't be insane, but I'd still like to make my code more efficient and compact (for the sake of minimization).

Time_Ticket.xlsm

I've attached my workbook and what I'm thinking (though I'm not sure how to handle) is to have 1 tab which queries and saves information to a separate tab (can be hidden). I understand Excel isn't the best program to do this with, but it's for work and not everyone has Access. So I could have (as I already do) a new week, clear week, and delete week button, and then a select week button which would pull up a userform of sorts where one could choose the week they would like to reference back to. The referential source would be all input information saved to a separate sheet when someone clicks new week or something.

Also keep in mind that this sheet is filled in, printed off, and cut up to be turned in on a daily basis (not by my choice - I'd prefer an all electronic system).
Thanks for any input!

Hi Phoenix,

Excel works best if the data is in a TABLE. That means it has rows of data that are the database records and columns which are the fields in the record. I'd take you information and put it on a single sheet. Each ticket would be a row of data. The fields would be: Date, Employee, Job#, Description, Time In, Time Out, Lunch Out, Lunch In. With a single table like described I'd then create the tickets and do all the work of your multiple sheets.

I believe you are doing way too much work by having the data on different tabs that correspond to dates. Do all your data entry in a single table on a single page.

You wanted some opinions and this is mine. Sorry if it isn't what you wanted to hear.

I agree with you Marvin. My previous attempt was a personal measure I created to type my time tickets as opposed to using the provided time cards which everyone must hand write their jobs daily. The tickets I've created on here aren't a database for multiple users, instead it's a personal database so the employee field wouldn't contain a unique value.

As you've suggested (and what I've ascertained on my own), I could create a table which stores all of this information: Date, Job#, Description, Times, Hours.
Where I'm concerned is the interface used to interact with this data. I would prefer this data to be in the background (a hidden sheet, for example) and one would select a week and the time ticket sheet is populated with all of the corresponding jobs, descriptions, clock times, and hours allocated to each job.
What I'm unsure of is how to easily obtain this information. It almost seems easier to create multiple tables to separate days and weeks. Each day has several jobs with their own descriptions, clock times, and hours and each week has a cumulative of the 5 days (meaning I would need a way to uniquely identify each day with its corresponding attributes).

Am I correct in viewing it this way?
Thanks.

Any other tips out there guys?
I appreciate any advice.