Registered: 13 years ago
OK, I have finished marking and will not be answering any further questions here
Some really good projects inbetween, some not user friendly and some requiring me to do minor fixes to get it to work, but generally no worries. Major fixes - you will know who you are - if it didn't work on your PC it did not work on mine and it will work nowhere else!
Functions in one page and then include the functions. Some did - others not. This is real imortant - if you need to fix something, you go to the function file and fix it in one file (as with the con file).
So I really looked for evidence that you gave a bit of thought to the structure of your application (how you made use of files etc).
A couple of problems with sessions, however, that will not make you fail. But if I get a parse error on every single page over and above a session problem then I fear you may have to redo some stuff.....
Some other minor and general remarks just to remember (you can't fail on these)
Always give thought to your navigation - if you can put 3 steps in one click do so.
If you make use of validation, do it before you submit the form. If not, it is a killer to have to go back and refill the whole form just because one field is wrong or incomplete. If you send them back, then the form must be completed with what was filled in (how to do was discussed elsewhere). At worst, ask people to use the browser back-button as oppposed to a back link.
If you update a field, echo the field in the text box rather than requiring the user to retype the whole word.
If one needs to edit a field, always make the field the link (e.g. make the coursename the link rather than making the course ID the link - it is unnatural. The course ID is used by the app - not by the user)
Male use of sub-directories e.g includes for include files. functions for function files (you may have more function files in future) etc.