Forms -1

A good way of looking at database applications and demarcating tables is the master / transaction view. Master tables contain relatively permanent data while Transaction tables capture data regarding business events typically interactions between elements of the Master tables. For e.g. in a University context, Master tables are maintained for students, faculty, departments, courses, subjects, etc., while Transaction tables will be for admissions, course registration, marks etc. In a Library, Master tables are for books, magazines, members, assets, etc., while transactions are for borrowing, returning, loss of book, purchases, etc. Can you tell what could be some master and transaction tables in a retail store? Library Management System Create the following Master tables: 1. tblMember Field Number Name DepartmentId DesignationId 2. tblBook Field AccNo Title Author Category 3. tblDepartment Field DepartmentId DepName 4. tblDesignation Field DesignationId DesName Data Type Text Text Data Type Text Text Data Type Text Text Text Text Data Type Text Text Text Text

And the following Transaction table 5. tblIssueReturn Field TransactNo MemNumber AccNo IssueDate DueDate ReturnDate Data Type AutoNumber Text Text Date Date Date

Though data can be entered directly into the tables, you should keep in mind, that especially for Transact tables, the sheer volume of data entry necessitates the utilisation of all the ways and means to: Reduce the monotony, Avoid entering data that have already been entered somewhere else, Also give ample scope for cross verification to avoid error and Reduce typing to a minimum

We will start with entering data directly into the Master tables; a few rows in each. And then we will create a functional form.