>Need assistance urgently. I am looking for assistance in define an approach
>for generating meaningless unique id's. Even though it is not listed as a
>requirement, each id must be unique. The customer specification is below:

Just a quite note on this. It might not be your answer but some important note you might consider. Base on what I read, it seems this will be treated as the primary key. If this is the case, you should have another field for a primary key. Assigning business logic to a primary key is not good. A primary key is a primary and should not be used other than for the primary key and establishing relationships across tables. Basically, a primary key is for internal use only. So, if I assume correctly, you might want to consider adding a new field for that. In such case, your backend contains already built in functionalities to achieve that automatically. As for your student field, you will have to create a procedure on your own and invoke that when you add a record.