Functional Dependancy:
programID --> progName, progFees, duration
studentID, collegeID --> name, address
prID --> prProgramID
facilityNo --> facilityName
collProgID, activityInstanceID --> scheduleID
collProgID, collegeID, programID --> strength, vacantSeats
activityID --> activityName
activityID, activityInstanceID --> startDate, endDate
applicationID --> studentID, activityInstanceID, place, applicationFees, applicationDate
studentID, programID --> entryID
studentID, activityInstanceID --> marksEntry, marks
prefID, applicationID, collProgInstID --> prefNo
feeReceiptNo, applicationID --> receiptFees, modeOfPayment, receiptDate, seatAllocation

The table below is in 1NF (no repeating groups)

Admission(programID, progName, progFees, duration, collegeID, collegeName, collegeAddress, prID, prProgramID, facilityNo, facilityName, activityID, activityName, activityInstanceID, startDate, endDate, collProgID, strength, vacantSeats, scheduleID,
studentID, studentName, studentAddress, applicationID, place, applicationFees, applicationDate, entryID, marks, marksEntry, prefID, collProgInstID, prefNo, feeReceiptNo, receiptFees, modeOfPayment, receiptDate, seatAllocation)

The tables below are in 2 NF (no partial dependencies)

TblProgram(programID, progName, progFees, duration, facilityNo, prID, prProgramID)
TblCollege(collegeID, collegeName, collegeAddress, facilityNo)
TblFacility(facilityNo, facilityName)
TblActivity(activityID, activityName)
TblActivityInstance(activityInstanceID, activityID, startDate, endDate)
TblCollegeProgramme(collProgID, collegeID, programID, strength, vacantSeats, scheduleID, activityInstanceID)
TblApplicant(studentID, studentName, studentAddress, entryID, activityInstanceID, marks, marksEntry)
TblApplication(applicationID, studentID, activityInstanceID, place, applicationFees, applicationDate, prefID, collProgInstID, prefNo, feeReceiptNo, ReceiptFees, modeOfPayment, receiptDate, seatAllocation)

The tables below are in 3NF (no transitive dependencies)

TblProgram(programID, progName, progFees, duration)
TblCollege(collegeID, collegeName, collegeAddress)
TblPreRequisite(prID, programID, prProgramID)
TblFacility(facilityNo, facilityName)
TblActivity(activityID, activityName)
TblActivityInstance(activityInstanceID, activityID, startDate, endDate)
TblProgFacility(facilityNo, programID)
TblCollFacility(facilityNo, collegeID)
TblCollegeProgramme(collProgID, collegeID, programID, strength, vacantSeats)
TblCollProgSchedule(scheduleID, collProgID, activityInstanceID)
TblApplicant(studentID, studentName, studentAddress)
TblApplication(applicationID, studentID, activityInstanceID, place, applicationFees, applicationDate)
TblApplicantQual(entryID, studentID (FK), programID (FK))
TblAppMarks(studentID, activityInstanceID, marks, marksEntry)
TblPreference(prefID, applicationID, collProgInstID, prefNo)
TblFeeReceipt(feeReceiptNo, applicationID, receiptFees, modeOfPayment, receiptDate seatAllocation)

That is what I have done now! but I am still got stuck when I design them! That means I make some mistakes ~ Anything correct to you! What wrong with that! You can point them out for me! and show me your solutions~ Pls, help me with that!
Thanks!