I work for a college and getting rid of a course is not just a decision taken by and administrator to click the delete button and the course is gone. What I did is that I have a function that checks if there is any students currently registered for a course. If there is then all the students have to be de-registered first, before the course can be deleted. If the course is empty of any registrations then the course can be deleted. This will help prevent courses from being deleted while there are still students registered for them. In a live system there will also be a financial app connected to the registration app. Think what will happen if a course just gets deleted willy nilly!!!
77911997 Wrote:
-------------------------------------------------------
> Hi All
>
> did any1 of you try to do the following
>
> 1. Allow a user to register for more than one
> course at the same time. (extra marks awarded for
> this)
>
if so, when deleting/editing a course, how can
> I ensure that not all courses linked to this
> student are deleted or edited, but only the
> intended one.
> eg. if a student registered 3 courses and wants to
> de-register 1 course. how can I make sure he/she
> doesn't get de-registered for all courses.
>
>
>
> 2. We give marks for added functionality that will
> require a change in the database structure, but
> which you do not need to code. For example, when
> you delete a course, you may want to delete all
> the students associated with that course. But
> after careful consideration, it makes sense to
> keep a history.
>
> did anyone try this?
