As mentioned before, without concurrency control the problems of lost updates uncommitted dependency, and inconsistent analysis are expected to occur. Since the registration database is a shared and classified resource, careful database management must be incorporated. Microsoft Access, provides three levels of looking. These are record locking, table and recordset locking, and opening with exclusive access For record locking, only the record currently i being edited is locked. For and recordset locking, an entire table or all tables underlying a form are locked while any user is editing any record in the form. Finally, opening with exclusive access, entire database is locked by a single user-change into single-user environment Microsoft Access automatically locks the record currently being edited even though the programmer did not predefine the lock mechanism. In registration database, since we always operate under multi user environment, the opening with exclusive access is irrelevant and will not be mentioned twice.
The most used mechanism in our registration database is table and recordset locking. Since this database is a relational database and has a quite complicated relation and query, recordset will be used for most of the time. As mentioned before about concurrency, the inconsistency about counting the number of students in class can be solved by using and recordset locking which will be referenced as lock. s the students decide to register any course, the lock is made active so that counting the number of students in each class is correct The reason why the original system locks the entire table is that it uses one table to store all records of who had registered for which courses. Consequently, the counting method
uses this table to count the number of students for each class. In other words, from Figure 2, the central database uses the table TREGISTER" to store and count the number of students in each course by using student ID and section as criteria for counting the number of students registered in each course. In our new system, the registration database stores records in table "TRegiterw Regradable" which is then used to count the number students in each course. DCount is used in Visual Basic code. Hence, if these tables are locked while any student is currently updating then, the lost updates problem can be solved