Admission : Name Address,age, photo,weight,fees,validity upto[calendar] 1) Create a DB with all details and set ID as key field and that

should be auto generated. 2) Imagine a mainscreen with Create button,view button,edit button ,fee button and attendance ,search and report button. If u press each button it will be navigated to the corresponding screen. 3) Create screen: all fields are input where ID is both input and output. 4) View screen: To view the details of the member , input can be name or ID . It should display all info. 5) Edit screen: If anything else to be changed or added this screen can be used.

Monthly fees : (Fees is not restricted to monthly, suppose if u wana see fees paid two months back?) Id num,[name,address,phto display], fees amount, current validity, validity upto[calendar] 1) I dont think to display address in this screen, because its already in Admission screen. It may contain ID, Fee amount and previously paid amounts and membership validity details. 2) So Imagine a screen with ID,fee as input and list of fee paid till date ,validity etc as output. I hope this will be usefull. Here fee should be both input and output..if someone pays fees the database should be updated. My question is...are you going to update the fee field with last paid fee? Or create a new record for fee paid with date? If u update a fee field u might feel difficult to see earlier paid fee..so second option is best..where it ll display list of fee paid till date. We need to check whether we can create many records for same keyfield(ID). Attendance : Id num, Validity date wid photo Messages 1. Your validity will expire in 2 days[shown 2 days b4 validity] 2. Your validity will expire in 1 day[shown 1 days b4 validity] 3. Your validity expired[from tat day onwards] 1) Screen should take ID as input and membership validity as output. 2) For validity check first we need to set calendar. Suppose a person is going to be a member for 3 months and two days due for his expiry..then program should calculate and If expiry is < 2 days...send message. Message can be hardcoded or store in file and retrieve it. Same way for other two conditions.

Search: To find id num thro name 1) I think no necessary for this. We embedded this option in view itself. User should click view and type either name or ID, all details should be displayed. May be if u wana advanced just use wildcards...like if u type a in name coloumn..all names starting with letter a will be popped down and select from that.

Report: 1. Attendance day wise/time wise/id num 2. Admission details day wise 3. Monthly fee day wise 4. Option to input/delete above all 3. 1) This is entirely program logic..just retrieve..read DC for particular input and generate report. Include print options in all.