php excel help..
Posted: Wed Oct 22, 2008 2:46 am
hii..
i'm developing an online portal for an university, which contain maodules like admin, accounts.
admin's job is to enter student,staff records and upload them to the DB.for example, if an exam was conducted for UG, PG students the admin has to enter about 3000 records to the DB.so i didnt find any use of using HTML FRONT END FORMS,now i'm using EXCEL as my front end form with password protection.
This predefined EXCEL has around 20 columns like name, branch, year, exam type, area of study followed by subject codes.
<b>NOTE:
-excel files are constants
-rows entered under the excel are also constants like name, branch, year.only marks obtained for concern subjects wil change and if a student promoted to next sem then year will change.</b>
my doubt is,
any application should save end user's time and effort.so html forms will be time killing, to enter 3000 records individually from html form will take min 40 minutes.
if i use html forms, my DB will be a normalized one. as my front end is EXCEL, normaliztion will create more excel sheets and many problems to delete or update single record.
so i'vent normalized my DB.
by doing this way, end user's time will be saved very much..can anyone tel me whether this idea is a good practise or not..
NOTE: END USER SHOULD NOT AFFECT is my motto./
many thanks,
pavan.p
waiting for ur opinions guys..
i'm developing an online portal for an university, which contain maodules like admin, accounts.
admin's job is to enter student,staff records and upload them to the DB.for example, if an exam was conducted for UG, PG students the admin has to enter about 3000 records to the DB.so i didnt find any use of using HTML FRONT END FORMS,now i'm using EXCEL as my front end form with password protection.
This predefined EXCEL has around 20 columns like name, branch, year, exam type, area of study followed by subject codes.
<b>NOTE:
-excel files are constants
-rows entered under the excel are also constants like name, branch, year.only marks obtained for concern subjects wil change and if a student promoted to next sem then year will change.</b>
my doubt is,
any application should save end user's time and effort.so html forms will be time killing, to enter 3000 records individually from html form will take min 40 minutes.
if i use html forms, my DB will be a normalized one. as my front end is EXCEL, normaliztion will create more excel sheets and many problems to delete or update single record.
so i'vent normalized my DB.
by doing this way, end user's time will be saved very much..can anyone tel me whether this idea is a good practise or not..
NOTE: END USER SHOULD NOT AFFECT is my motto./
many thanks,
pavan.p
waiting for ur opinions guys..