Your database and table structure are ALL WRONG. Indeed, it is obvious that you have not even begun to understand relational databases at all. Go and read some articles or books on database design and data normalisation.
start here database normalisation and design techniques
Wikepedia
MySQL: an introduction to database normalisation
Your db design would be 1 table for all weeks, all days, all entries, and all members if more than one person.
single user
table calory intake
cal_id integer autoincrement primary key
when date-type
meal text-type
food text-type
qty decimal-type
From that you can use the date to work out calory intake for a day, a week, a month, or a year just by grouping on a date period: from-to or between dates.
You could also work out the intake for a particular meal like breakfasts, or the most frequent food, etc.
You could even extend it with another table that give the calories for a given quantity of a particular food, eg Bread 250 calories per 100 grams, and then use that to calculate the calories for a given meal, or the average calories taken in at lunch each week and suchlike. Make it easy to pinpoint where the fat is being taken on and where the effort should be directed.
Read the articles I have linked to and the whys and wherefors of this will be obvious.
