I had a look at your db - and codewise, you were close. And Scott is right, you need to look at normalization before continuing. You have one table - essentially a flat file. You need to add several more tables. For each of your drop-down lists that you have in your table, I would suggest another table containing those items, and then a FK (number), pointing to that table.
Once you have that completed, the rest of your application will become simple.
Work on properly structuring your db first, then functionality.
To get the code to work which you currently have, you just need to rename 'check36' to 'chkDept'. Ensure that you dont accidently name the label 'chkdept'.
Again, just to hammer down the point, normalize your db - it will save you time and effort in the future.
Hope this helps,
EDIT : just saw your post.
- tlhHoursType: Is this a new table name that I need to set?
- FK (what this mean)
Do I have to create two fields in HourType (one for Regular and another for OT)
tluHoursType - This is the name of another table. I'm assuming that the prefix is either "tlu" for Table LookUp, or a typo ("tbl").
FK - is a foreign key. It is the numeric value of the index of the table it points to. This way, you can use joins to display the text value if required, and store only the bare essiential number in your main table.
You only create one field in HourType, but as many ENTRIES in that table as you need (one for reg, one for OT right now). Then, in your main table, in your HourTypeID field, you would place the number which represents the index in tluHoursType.
Edited by: adamsherring on Tue Jan 16 14:32:29 EST 2007.