Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
management
documentation
Computer coursework
A detailed coursework oI the library management
system, covering areas oI analysis, design, testing,
implementation and evaluation oI the DBMS.
Usman Ahmed
2/28/2011
Library database management system
2
Acknowledgement
It is a privilege to express my sincerest regards to my teacher Mr. Hashmat Ali Ior
his valuable and meaningIul inputs, able guidance encouragement whole hearted
cooperation and constructive criticism throughout the duration oI my project.
I owe my deepest gratitude to the librarian who helped me out, cooperated and
oIIered me any sort oI help I required in the completion oI this project.
I am indebted to my many oI my classmates whom I worked with and together we
solved numberless problems and completed this project.
This project would not have been possible without the help coordination and
support oI all these people. Last but not the least, I pay my respect and love to my
parents and brothers Ior their love and encouragement throughout this project as
well as my entire liIe.
Library database management system
3
Library database management system
4
ProbIem identificution
INTRODUCTION
Divisional public school is renowned institution and is known Ior its excellent and outstanding
perIormance oI its students in academics. Lately the new administration committee has put a lot
oI Iocus in increasing the general knowledge and creativity oI students. For the purpose the use
oI library has been encouraged and promoted.
The school has a small library that has till now been providing students with books. Although
the whole school management system is computerized but the library is based on manual system.
Most oI the library`s stock comes Irom diIIerent book shops. Books relating to syllabus,
entertainment, poetry, religion and philosophy are all present here. All the records are stored on
Iiles and registers. Previously, there were about 10-15 issues per day, the total number oI
members was around 150 and a couple or more membership requests were put Iorward each
week.
The library, in size, is quite large. It has proper book racks onto which the books are placed.
These racks spread all over the library and are round about 25 in number. Each rack contains
about 200 books. 3 racks have been assigned to English, 3 Ior Urdu and Islamic studies, 1 Ior
computer studies and 5 Ior sciences. Other racks include arts, general knowledge, history and
one rack Ior new arrivals.
The librarian is the only person who manages all the stuII in the library. He has been charged
with the duties to manage the membership, books and also with issuance and return oI the book.
In addition to these things he also has to look aIter the classes who arrive at the library each day.
Managing the students along with looking aIter the management has always been a problem Ior
the librarian but so Iar the things had been going quite well.
With recent encouragement Ior the use oI library, the numbers oI memberships has improved
dramatically. Also more Iinance has been provided to the librarian to buy books that concern the
students. All these measures have incremented the amount oI work Ior the librarian. This has
made this manual system ineIIicient and diIIicult to manage. Apart Irom this there are several
other issues relating the manual system that will be covered later.
Library database management system
5
ProbIems with the system
In order to identiIy all the possible problems with the existing system I had to investigate the
system deeply. For the purpose I observed the system closely by sitting with the librarian during
the work hours. I inspected any bits oI paper or Iiles which are used in the present system. Apart
Irom that the members oI the library were also asked questions about their satisIaction and any
suggested improvements Irom their side.
There are various problems with existing manual system oI library and these are:
O Sometimes inIormation was not Iully provided which led to incomplete records.
O There was a lot oI relationship between diIIerent registers but there was not a way oI
creating these relationships.
O Sometimes important inIormation was lost because data is hardcopy and is also misplaced
easily. The registers are sometimes torn or lost in other registers.
O There is no backup Iacility and there was a chance oI losing oI data in case oI any mishap.
O The manual way oI recording the data was ineIIicient and sometimes human error prevailed
which led to incorrect oI data.
O Updating particular records was diIIicult as there was not an easy way to Iind a particular
Iield.
O The manual system was way time consuming.
O The data was to be Iilled in twice Ior each update on diIIerent registers and this also took more
time.
O Problems occurred in recording the data as there were times when registers were mixed up
O There was only one librarian to deal with everything which caused long queues oI students.
O Preserving old and current data was also a problem.
O Big registers were needed Ior storing data.
O As there were so many registers there was no way oI searching Ior typical type oI stock
item.
O Sometimes inIormation was to be provided to authorities and Ior that either the original
document was sent or it was photocopied. This sometimes delayed proceedings or
documents were lost.
O II Iiles were put back into wrong place Iinding it again was a painstaking task.
O System security was also impossible.
Library database management system
6
PersonuI observution
During the time I spent investigating the system, I witnessed a number oI small problems which
because oI mismanagement and lack technical skill had encumbered to a potential drawback in
the system. The librarian had once been nice enough that he oIIered me to take up his place Ior
one day. Since I was already told about all the operations and I had myselI investigated a lot, I
Ielt this job would be a piece oI cake. As the Iirst member came to borrow a book, the problems
started Irom that moment. Only aIter I took out the heavy register out oI drawer and Ilipped piles
oI pages, then could I perIorm any Iunction. I made several mistakes and to correct them I had to
rub it or cut it which looked messy and untidy. I remembered at this moment that ease with
which these operations could be perIormed using a computer. Sometimes I had to come out oI
the seat and walk to diIIerent drawers and tables. One oI the worst problems was data
duplication. I perIormed the job with attention at Iirst but the job proved to be monotonous as I
went on. Later I noticed that librarian also went through the same Ieelings when he did the job.
Then I concluded that there was an urgent need to take some remedial actions. For that I drew up
a list oI objectives to be met by the new system.
Library database management system
7
Obgectives of the proposed system
eeping in view all the problems that exist in the manual operation oI the library system, a list oI
objectives has been drawn up so that the new system is built on the basis oI these requirements.
The objectives list is as Iollows:
O Building a system that is user Iriendly.
O #educing time consumption when perIorming any kind oI Iunction.
O Minimizing human error and to produce accurate results.
O #educing the use oI paperwork which is comparatively expensive and takes a lot oI
space.
O ew system should be easy to use with layouts that easily guide the user to his speciIic
tasks
O To reduce the work load oI librarian and spare him more time to look Ior books in-
demand oI students nowadays
O Providing backup Iacility to avoid loss oI data.
O Improving Iile maintenance.
O Making editing easier.
O Sorting and searching Ior Iiles like late returns are easy to Iind
O The new system should be Ieasible enough and better in the long and short run
O Use oI validation checks to ensure data integrity
O utting out the need Ior adding data twice
O Searching data is very quick, especially with the Ieature oI cross reIerencing; data related
to diIIerent Iields could be merged together in a meaningIul Iorm.
O #educing the amount oI space taken by the registers.
O #etrieval oI data is easier and printouts could be used in case a hardcopy is needed.
O #estricting access to personnel Iiles Ior anyone except the librarian.
Library database management system
8
Description of eisting soIution
A library system may look ordinary to an outsider but iI you go deep into the system one will
Iind a complicated network oI recording inIormation taking place every day. The existing system
works as Iollows:
Membership Procedure
When a student comes Ior membership he brings with him his passport sized picture, the last
submitted Iee voucher and a dollar which is the registration Iee. AIter he has been veriIied as a
student who has paid all his dues, his voucher and picture is kept to Iill in his inIormation and he
is given a one day time to check back and receive the membership card which looks something
like this:
A student is now a member oI the library and can borrow books any time. The librarian Iills in
the inIormation about the student in his register under the respective class page. The membership
oI the library expires with the start oI the ew Year. Students have to apply Ior the membership
now again.
Library database management system
9
ook Identificution
The librarian, however, has no way oI keeping track oI all the books he has. Every book has a
stamp on it depicting its book code and there is no other way oI proving that the book belongs to
the library. When a new book is bought Ior the library a stamp with the book code is pasted on
the Iirst page and is put on the shelI relating to that topic. #ecord oI the books are not present,
instead, when book is lent this inIormation is written on membership card oI the student along
with the due date and on the other hand on the registers that hold the students issue details.
Muintuining the DetuiIs
The librarian has to go through all the pages oI the register at the end oI the day to see iI due date
oI any student has arrived. A memo is made and on next day he notiIies the student about it. The
head master or the authorities sometimes demand the inIormation about how many books were
lent, or how many students have now become the members oI the library. This is a painstaking
task. The librarian again goes to the register that holds issue details or membership details, then
makes a list out oI it and sends it to the headmaster. It consumes a lot oI time and other things are
delayed because oI it.
ooks Record
The librarian was now asked to make records oI all the books he has in the library. On this he
told them about the diIIiculty and so other options were looked besides this manual system.
Library database management system
10
EvuIuution of eisting soIution
The existing system is completely manual and thereIore involves no use oI computers
whatsoever. All entries, including membership details, lent books, student`s issuance history and
other data is made on registers. The system could be divided into books and members, and
issuance.
ook Record
The record about the books is a major lapse in the manual system. This means iI a book gets
displaced or any student steals it than librarian would have no way oI knowing the whereabouts
oI the book. The only book records with him is the books that have been issued and even those
are Iound in the students issuance history not in any separate registers pertaining to books. The
way books are held needs much improvement.
Membership
Member`s record is comparatively better than the books record. These records are usually
complete but still updating them demands time. Since these records are under class section so
sorting and Iinding them takes time. A Iaster data entry and editing system is needed Ior this
Iield also.
Issuing und Returning ooks
Issuance system is also a mess. Although the register Ior issuance is Iairly complete but this
takes most oI the time oI the librarian, mainly because the records are not easy to search. Piles oI
pages have to be Ilipped and this process pages are sometimes torn. #ecords are organized but
since they are arranged with reIerence to class so search criteria any other than class is an
awesome task.
SeneruI ProbIems
Apart Irom all these systems there are other general problems:
O Time consuming: the storing oI data on papers requires a lot oI time, it oIten delays the work.
O A great number oI Iiles are created each day. Updating and searching an item oI data is a
very tough and hectic job.
O There are a lot oI Iiles created in the paper based process so a no. oI Iilling cabinets needed
Ior storing Iiles. This requires a large space and a high maintenance cost.
O Because oI the paper based system, there are Irequent mistakes in daily calculations. There
are also Iaults in date calculation which makes report generation diIIicult.
The Iew advantages that this system might have over the computerized system are:
Library database management system
11
O Everyone is Iamiliar with the paper based system because it does not require any kind oI
technical skills.
O The current system is cheaper since it does not require any electrical equipment.
O II any changes are made to the records in the registers by anyone but library, this is
noticeable.
The librarian works as hard as he could. The way this system could be improved is to have
someone who could share his workload. The inIormation on the registers needs to be reorganized
displaying them with the criteria Ior which most Irequent searches are made.
Library database management system
12
Description of other possibIe soIutions
ProperIy munuged munuuI system
II the existing manual system is properly managed by the authorities, then the ineIIiciency oI the
system can be improved. This can be done so iI the staII needed to manage the library is
increased i.e. an assistant Ior the librarian. He could help to share the workload. So when the
librarian is sorting out membership requests he could look into other areas.
Another way that would improve the manual management is Ior the librarian to be paid Ior extra
hours he spends in the library aIter the school timings. In this extra time he could sort all the
mess and no work would be leIt pending Ior a later date.
TuiIor-mude Iibrury munugement system
This is also the proposed solution. It is a careIully designed database management system that
would be run on computer. The librarian would use a keyboard and a mouse as input devices
which are quite easy to use. All the requirements oI the librarian are met and this database would
keep all the data organized. DiIIerent areas have been linked so perIorming searches to Iind data
related to several tables is easy. There will be buttons on the Iorms that would guide the user to
enter, edit or delete records. They could be used to issue and return lent books. #eports oI all the
issued books can be viewed or printed on a single command. A login page has also been set up
so that whenever the librarian is away Irom the computer system he could log out and people
won`t access the data.
Off the sheIve Iibrury dutubuse system
This is also an option worth looking into. The authorities could buy a library database system
Irom a shop and implement it. These databases are designed keeping in mind the needs oI the
librarians and most oI the related topic. There won`t be much diIIerence in the ways the proposal
system and this system would operate since both are nothing but the same things but the
diIIerence would be the data stored in the database. The librarian would use just a computer Ior
all management. This might also be a bit cheaper than the proposed solution.
My evuIuution
eeping in mind all the aspects oI the old systems, objectives oI the new system, deIiciencies,
area oI importance and everything else, it would be best to adopt Ior the system I propose. It
would cover up every aspect oI system and added to it, it would provide security Ior personal
Library database management system
13
data. Backup would be an easy job and any chances Ior loss oI data can never materialize. The
amount oI space used by the registers would no longer be a problem. The computer system could
also be used Ior other purposes i.e. it could be used to order books online or Ior other purposes.
A potential disadvantage would be the dependence oI the library on computer since iI it breaks
down all proceedings would come to a halt. But arrangements Ior this could also be done. In
view oI all the above points it is best considered to chose my proposed solution to be chosen.
Library database management system
14
Library database management system
15
Action pIun
With the start oI the new session on April 14
th
, we were introduced to the project work and its ins
and outs. We already had an idea oI databases and how they looked like but never had an
experience oI making one. From a list oI topics we had, I chose library management system
mainly because oI the ease with which I could collect and gather all the data. The school library
served the purpose so I decided that my library project should be based on the school`s library.
My teacher introduced me to the librarian and he was willing to help. I started my investigation
on Iirst oI May. In the IiIteen days we had beIore we were told all the things that should be
considered and a general introduction oI database soItware was given. I decided to choose Ms
Access mainly because it was very user-Iriendly and easy to use. From the start oI next month I
started to spend the breaks with the librarian talking him out about the system and observing how
are the things done currently. I always had a copy to note down any Ilaw or a novel operation
perIormed by the librarian.
Within Iirst week I go to know a number oI things. I completely understood how the processes
take place yet I spent another week to know about all the Ilaws in detail. Finally a prepared a list
oI all the problems he Iaced and accordingly started to devise a list oI objectives that the new
system should achieve. onsidering the problems I proposed a Iew solutions but the most
reasonable was computerized database.
AIter I was done with the investigation phase, the time now came to make the tables. I had some
prior knowledge to it and some help was provided by our teacher and the internet. I started to
design how the new system would work. During this period I Irequently visited the library to
keep myselI aware oI the requirements oI the library. All the validation rules were made and the
method about how the proceedings would take place was devised. It took me about a month and
then I moved onto the development oI the database. I made the Iorms and tried to make them as
much user-Iriendly as possible. Then I made the queries based on the inIormation I had collected
and made reports Irom them. The switchboards were careIully designed and aIter that the
development oI the soItware Iinally ended.
To ensure that the new system worked perIectly well, I perIormed some testing on the system. I
tested it with normal and abnormal values and all other mistakes that manual system made. This
was done quickly within a week. AIter that I meticulously prepared the user documentation
taking in consideration all the possible requirements and needs oI the librarian. This took me a
couple oI weeks. Firstly the method oI implementation had to be careIully decided upon. The
reason has been stated in the respective section. To implement the system the librarian had to be
trained. This was done partly by the user documentation I prepared and the rest was done under
my supervision. AIter the librarian had been Iully satisIied the new system was Iinally
implemented. I then kept a close watch on the system in Iirst couple oI weeks to see iI it is
Library database management system
16
working perIectly Iine. The system was also being evaluated at the same time and aIter observing
Ior two weeks I prepared my evaluation. And when this passed the job was Iinally over.
5/1/2010 5/21/2010 6/10/2010 6/30/2010 7/20/2010 8/9/2010 8/29/2010
system investigation
design
development
testing
user documentation
implementation
evaluation
Library database management system
17
System fIowchurts
Structure diugrum
Book`s
record
Member`s
record
Issuance
record
Library
management
system
#ecord oI books,
members and
issuance
Library
database
User /
administrator
#esult
Library system
Book management
Member
management
Member
Issuance/
return
Library database management system
18
Muin System fIowchurt
Username/
password
Start
Check
Username and
password correct
Username and
password incorrect
Main menu
Member
operations
Book
operations
Issue books Return
books
Book
operations
Member
operations
Issuance table
Library database management system
19
Member operutions
Username/
password
Start
Check
Main menu
Enter new
member
Edit member`s
data
Member`s
issuance report
All students`
report
Class wise
member`s
reports
Username and
password correct
Username and
password incorrect
Member table
Member
operation
Library database management system
20
ooks operutions
Username/
password
Start
Check
Main menu
Enter new
book
Edit book`s
data
Books issuance
(report)
All books
report
Books by
author (report)
Username and
password correct
Username and
password incorrect
Books table
Books table
Library database management system
21
Issue/return und issuunce history
Username/
password
Start
Validate
Main menu
Issuance
history
Issue a
book
Return a
book
Issues by members
(report) (report)
Issued books
(report)
Issues by books
(report)
Returned
books (report)
Username and
password correct
Username and
password incorrect
Library database management system
22
Progrum fIowchurts
Enter u new book/member
DeIete record of u book/member/issuunce
Start
Login validation
Books record saved
in database
Book/member/
issuance report
updated
Start
Login validation
#ecord deleted
Irom the database
Book/member/
issuance report
updated
Book/member Iorm in add mode.
Enter the details
Is data
correct?
Show error
statement
o
Ye
Book/member Iorm in add mode,
issue Iorm
Delete record
Library database management system
23
Modify book/member/issuunce record
Seurch u member/book/issuunce by ID {unique code}
Start
Login validation
atabase
Book/member Iorm in edit mode,
return Iorm
Select/type ID
Is record
present?
Display
record
Yes
Display error
statement
o
Start
Login validation
Books record saved
in database
Book/member/
issuance report
updated
Book/member Iorm in add mode,
issue Iorm
hange details
Is data
correct?
Show error
statement
o
Yes
Library database management system
24
Lend u book
View reports
Start
Login validation
Issue record saved
in database
Show report
Issue Iorm
Enter details
Is data
correct?
Show error
statement
Yes
o
Start
Login validation
Enter parameter
value
Is value
correct?
Yes o
Show empty
report
Issuance report
updated
Library database management system
25
Method of soIution
Dutubuse design
The Iollowing three tables are used in this database.
1. Members inIormation
2. Books inIormation
3. Book administration (issue/return table)
Member informution
This table will keep all the relative inIormation about the students who hold the membership oI
the library
The Iollowing table shows the data type and it also list its character length. These data types will
act as validation check while also insuring the integrity oI data and the character length will help
to reduce the space
Table Iields Data type haracter length
#ollno text 000000\-00;;
ame Text 30
lass text 4
ontactno text 000\-0000000;;
e-mail text 40
Membershipdate Date mm/dd/yyyy
O #4*34
This is the unique Iield Ior this table. This Iield records the roll number oI the student that is
given to him by the school It is also indexed so that Iast searching can be done. Duplication oI
this Iield id not allowed.
Library database management system
26
O Aame
This is the name oI the student. The data type is text which is best suited to the record name. this
Iield can record up to 30 characters oI names.
O ass
The class and section oI the student are recorded in this Iield. This inIormation does not take
more than 4 characters oI length
O 439ac9*34
II the librarian needs to contact a student, than this Iield could be used. An input mask has
already been setup so that it can be easily entered.
O mai
This is another way to contact the student.
O embership*/a9e
This is a date type Iield. It records when did the student became the member oI the library. A
calendar opens iI selected on this Iield which makes it easier to select the date.
Library database management system
27
ooks informution
This table keeps track oI all the books that the library has. The Iollowing table shows the data
type and it also list its character length. These data types will act as validation check while also
insuring the integrity oI data and the character length will help to reduce the space
Table Iield Data type haracter length
Bookcode Text 5
Title Text 25
Author Text 30
ategory Text 15
Price urrency
O 44*c4/e
This is the unique Iield Ior this table. This code has been given to the books by the librarian and
is unique Ior each book. It is also indexed so that Iast searching can be done. Duplication oI this
Iield id not allowed. All the book codes are 5 digits long so the character has been set up to 5
digits.
O %i9e
This is the book name
O :9h4r
This is the name oI the author. A search criterion has been set up by the author name to view all
the books oI an author iI required in a report Iorm.
O a9eg4ry
This tells which category this book belongs to e.g. 'Mathematics. A search criterion has also
been set up to Iind all the books related to a particular category.
O !rice
This is a currency type Iield. It is used in case a book is lost by the student. He has to compensate
the cost price oI this book.
Library database management system
28
ook udministrution {issue/return}
This table is responsible to keep track oI all the books that have been issued. Another Iunction oI
this table is to record is the book that has been issued has been returned or not.
The Iollowing table shows the data type and it also list its character length. These data types will
act as validation check while also insuring the integrity oI data and the character length will help
to reduce the space
Table Iields Data type haracter length
Issuanceno Autoumber
#ollno Text 000000\-00;;
Bookcode Text 5
Issuedate Date mm/dd/yyy
#eturndate Date mm/dd/yyy
#eturn Yes/no
O ss:a3ce*34
This is the unique Iield Ior this table. It is Autoumber. What that means is that there will be an
increment oI one each time a new record is entered. This issuance number is also told to the
students so that whenever he returns the book, the librarian could easily search Ior the issued
record trough this number.
O #4*34
This Iield is the unique Iield oI the members table. A drop down appears Ior this Iield and a
member is chosen. Only the roll no that is present in the members table could be chosen here.
This reduces the chance oI mistakes.
O 44*c4/e
This Iield is unique Ior the books table. A drop down appears Ior this Iield and the required book
is chosen. Only the bookcode that is present in the books table could be chosen here. This
reduces the chance oI mistakes.
Library database management system
29
O ss:e*/a9e
This is a date type Iield and the day when a book is issued is recorded here. A calendar appears
on this Iield iI selected and this reduces any chance oI mistakes in entering the date.
O #e9:r3*/a9e
This Is also a date type Iield. Initially the due date oI a book issued is recorded here. AIterward
when he book is brought back this date is changed to the today`s date. A calendar also appears
here.
O #e9:r3
This is a yes/no Iield. It tells iI a book that has been issued has returned or not. A couple oI
reports have been made with this Iield as the criterion.
O ReIutionships
Library database management system
30
Queries
O Issued books
ield Tab
le
escription
Issuance no Issu
e
This would indicate the issuance number oI books issued.
Bookcode Issu
e
The book code oI the issued book
#ollno Issu
e
The rollno oI the student who has been issued the book
Issuedate Issu
e
The date when the boom was issued
#eturndate Issu
e
The date when the book has to be returned
#eturn Issu
e
This is the deIining Iield and and has criterion 'o. So the books that
have not yet been returned would appear on the report based on this query.
O Returned books
ield Table escription
Issuance no Issue This would indicate the issuance number oI books issued.
Bookcode Issue The book code oI the issued book
#ollno Issue The rollno oI the student who has been issued the book
Issuedate Issue The date when the book was issued
#eturndate Issue The date when the book has to be returned
#eturn Issue This is the deIining Iield and and has criterion 'Yes. So the books that
have been returned would appear on the report based on this query.
Library database management system
31
O ooks issuunce history
ield Table escription
Issuanceno Issue This would indicate the issuance number oI books issued.
#ollno Member This is the deIining Iield Ior this query. It has the criterion '|Enter roll no|. so
the issuance history oI the student whose rollno has been entered will appear
here
name Member The name oI the student
bookcode Issue The book code oI the book issued
Issuedate Issue The date when the book was issued
#eturndate Issue The date when the book has to be returned
#eturn issue This will indicate whether the book has been returned or not
O ooks issuunce history
ield Table escription
Issuanceno Issue This would indicate the issuance number oI books issued.
bookcode books This is the deIining Iield Ior this query. It has the criterion |Enter book code|. So
the issuance history oI the book whose bookcode has been entered will appear
here.
Booktitle books The title oI the book whose record is being shown
#ollno issue The rollno oI the student who has been issued the books
Issuedate Issue The date when the book was issued
#eturndate Issue The date when the book has to be returned
#eturn issue This will indicate whether the book has been returned or not
Library database management system
32
Method of soIution
The record oI all the books is entered into the books table. Description oI each Iield and its
purpose has been also been explained. The inIormation about members is also added to the
members table and its description has also been given. AIter both oI these steps have been done
then we look into the issuing oI books. The unique Iield here is the issuance number which is set
as an Autoumber. The other Iields are rollno Irom the member`s inIormation table and book
code Irom the books inIormation table.
ow when iI a student has to issue a book either he wanders all around the library observing any
book oI interest or he goes directly to the librarian telling him the name oI the book. II the
student selects a book Irom the library as in the Iirst method, in this case the librarian enters the
book code Irom the cover oI the book. The student tells his rollno. AIter both oI this
inIormation has been entered, the librarian selects the issue date as the current date and the due
date oI two weeks Irom that day. With the other method when the student tells the name oI the
book. The librarian goes to the books table. He enters the name oI the book in the navigation bar
at the bottom oI the page. II that books is present than that record Ior this book appears. The grid
below the Iields also indicates iI this book has already been issued or not. With all the
inIormation now available the book is issued.
When a student comes to return a book he tells the issuance number that had been given to him.
In the return table, that issuance number is selected Irom the combo box. The record appears and
in the return Iield the option yes is clicked and in this way the book is returned.
Sometimes the members don`t return the books on time. To check all the delays there is a report
Ior this. In the issuance history in the main menu there is a button named 'issued books. This
report shows all the books that have currently been issued. A sort Iilter has been applied to this
report according to which the return date which is closest to the current date appears on the top.
In this way the deIaulters are easily checked. A notiIication can be sent to them in their class or
there contact number or email id.
There other reports that include the issuance history oI an individual student, issuance history oI
a book, all the returned books, all members report, books report and many others.
Library database management system
33
Hurdwure requirements
A personuI computer
A system box that would contain the Iollowing items
O Pentium 4 with 3.2 GHz processor
O 1 GB ram
O 40 GB hard disk
O D drive
O 1 GB USB/Ilash/pen drive
A good processor would ensure smooth operation oI the database along with the computer
system. It is the brain oI the computer and all processes are done inside. So iI a processor is
good, commands will be processed at high speed.
#andom access memory is a Iorm oI computer data storage. #AM (random access memory) is
the place in a computer where the operating system, application programs (including the library
database system), and data in current use are kept so that they can be quickly reached by the
computer's processor. This large amount oI #AM will help in multi-tasking. Also the soItware
used (Ms Access) is heavy soItware. Its basic requirement is 512mb oI #AM. For the computer
to be used Ior other purposes also this much amount oI #AM would justiIy the needs
Although the database soItware requires very little space but other computer programs will need
it. The operating system, application programs and other data all require space so 40 GB will be
enough to cater all the soItware and programs. This is a huge advantage with the computer. The
space which all the registers and the paperwork needed is no more wasted. The amount oI space
the database would take is many thousand times lower than that oI the total space available.
D-#om drive will be needed to install the database soItware initially. Other application
soItware such as an Anti-virus program or other documents or Iiles Ior entertainment can all be
installed using a D-#om which will be inserted into the D-#om drive.
USB/Ilash/pen drive could be used to make backups oI data. ertain documents and Iiles can
also be copied Irom the other computers with this USB.
Library database management system
34
PeripheruI devices
O "WE#TY keyboard
O Optical mouse
O Inkjet printer
O 'DU
A "WE#TY keyboard should be used to enter data into the system. InIormation about the
members, books and issue are all input using a keyboard. With little practice, data entry with a
key board is quite Iast and this saves time. Time spent searching Ior pen or a paper is also cut
out.
An optical mouse should be used to translate the movement oI the cursor on the screen. It will be
used to open and close Iorms and navigate through to required pages. Doing or opening speciIic
applications or programs I easier and quicker using a mouse. Flipping piles oI pages or searching
Ior registers Irom the drawers is all done by this single mouse Ior the computerized system.
An ink jet printer should be used because printouts oI reports will regularly be needed. Inkjet
printers are cheaper to buy and the quality is also good. The running cost oI inkjet printer is high
but since sporadic printouts are needed, usually at the end oI the month so this won`t be a
problem. This printer can also be used by other staII oI school to print their documents and so it
can serve Ior multiple purposes.
A visual display unit oI at least 1024x768 resolution and 17 or larger size Ior the output. This
will ensure that the quality is very good and a large size would reduce eye strain.
Library database management system
35
Softwure requirements
SoItware selection describes the soItware to be used Ior the system. Its purpose is to choose the
appropriate soItware that would support the database to Iunction as smoothly as possible.
Operuting system:
I would recommend the use oI windows XP service pack 2 Ior the system. It is a well known OS
and uses GUI that makes it very user Iriendly. There are many advantages oI windows XP a Iew
oI them are given below:
O It supports most oI the hardware without need oI external drivers.
O It oIIers good GUI as compared to older versions.
O It supports wireless networking
O Many applications are developed Ior windows only and on other OS
they do not work
O Windows XP oIIers universal plug and play Ieatures
O The availability oI this is very high.
O It oIIers universal solution to OS needs and there are no compatibility
issues in this case.
O The school has the site license. What this means is that the school can
make limited copies oI the soItware they have Ior the use in the same
organization. This OS was bought Ior use in computers in computer
lab and also Ior administration. Purchasing a site license is cheaper than buying multiple
copies oI a program.
Microsoft office 07
Since the database is designed on MicrosoIt access 07 so only it can be used. MicrosoIt access
has been chosen Ior a number oI reasons:
MicrosoIt Access is a database soItware program that makes manipulating data manageable Ior
users oI many skill levels. You can input data and sort Iilter or group inIormation according to
your needs. It's particularly useIul when there are thousands oI records and sorting through them
individually would take hours. Access allows you to obtain the inIormation quicker by providing
a Iew commands to tell the program what is being sought. #eports can be created, too, that pull
inIormation out oI the database according to the project parameters. For example, inIormation on
a member`s age, sex, class, address, email address, phone number and cell phone number may be
listed in your database. However, demographics about the client may be the only thing necessary
to complete a given project. You can then build a report that will extract members by class and
membership status.
Library database management system
36
MS access can be used with MS word Ior mail merge, pulling out the contacts Irom the database
and then Iixed into each letter separately. A little bit oI planning will go a long way Ior the best
use oI an Access database. First, it needs to be Iigured out how the database would be used.
ext, all inIormation is gathered to be input into the database and is organized into categories,
each oI which will become a table. Data is input into the tables, which will become columns and
then relationship are made between the tables. Finally, normalization rules are applied to make
sure the tables are structured correctly.
MS Access is the most widely used desktop database system in the world. It is excellent soItware
Ior making and then using the database. Its best point is the ease with which all Ieatures can be
accessed. It is the most user Iriendly soItware Ior database management system. Other
application soItware in this package could be used Ior number oI purposes, e.g. MicrosoIt word
could be used to type letters to authorities.
UtiIity puckuge
aspersky anti-virus should be used to eliminate and block all viruses that try to enter into the
system. It is well known soItware and doesn`t slow down the computer much. It is Ireeware
soItware and the scanning speed is Iast compared to other packages. It will ensure that the
personal data is protected Irom any types oI viruses and thus the object Ior the saIekeeping oI
data will be achieved.
Library database management system
37
Library database management system
38
Method of soIution
System impIementution
In the system implementation we enhance the previous system with new system. Activities Ior
implementation includes converse oI data to new system Iiles, Iinal training oI the end user and
the transaction Irom the old system to the new system. At this point the end user and the
management actually begin to use the constructed inIormation system. System is evaluated by
organization. The purpose oI these evaluations is to determine iI the system operates as new, and
iI the beneIits are anticipated. The main steps are:
O Final document
O The end user training
O System changeover
FinuI documentution
The Iinal documentations include collection oI documents, capabilities, design, operation and
maintenance oI the system. The procedures cover entering the data, directing activities, making
inquiries and distributing reports. This part oI the implementation will be covered later under the
user documentation
The end user truining
The librarian should receive training that is appropriate to his role.
BeIore training we should make some guidelines like:
O Prepare manual and tutorial Ior training.
O Develop distinct training programs Ior diIIerent employees group.
O Provide Ior learning by bearing, seeing and doing.
System chungeover
System changeover is the process oI putting the new inIormation system into operation and
retiring the older one. There are basically Iour method used to chance over the system.
1. direct implementation
2. parallel implementation
3. pilot operation
4. phase change over
Direct impIementution
The change Irom old system to the new system occurs instantaneously. One day the old system is
used and the next day the new system is in operation and old system is discontinued. This
Library database management system
39
method could be implemented only when the new session starts because at that time all the
memberships would expire and the new memberships would be entered into the new database
system. With the time spared he could enter the records oI all the books.
EvuIuution of direct impIementution
The chieI advantage oI this approach is the cost consideration as one system is dropped and the
other is started at once. o backup or temporary system cost is spent. It shows the error iI any, at
once. And this could be havoc. II the data oI the whole month is Ied into the system and then due
to some problem the database won`t start then this could bring the whole process to a halt.
Phused impIementution
With phased changeover, we implement the new system in pieces or modules rather than
implementing a new manuIacturing system all at once until the entire system is working in the
organization. For instance one may decide to look at the books section Iirst and get this running
beIore he deals with other areas oI the library.
EvuIuution of phused impIementution
In case an error occurs in phased implementation, the whole oI the system is not aIIected,
mistakes are easy to sort out since they occur only in small part oI the whole project. Data losses
in such case in also smaller than compared to direct implementation. Once the one part oI the
database has been implemented and is running Iine, then others parts maybe introduced as well.
One lapse with method is that it takes much longer and the beneIits oI the new system are
delayed.
PuruIIeI operution
With parallel operation the new and the old system are run alongside each other. The librarian
would have to Iill in all the details Iirst manually on registers in the manual system and then on
computers using keyboard and mouse. The output data is generated by the new system and is
compared to the equivalent output Irom the old system. When everyone is satisIied that the
newly developed system is operating correctly, the old one is retired.
EvuIuution of the puruIIeI operution
Parallel operation is not an option that can be looked into. The new is being implemented
because oI the increased workload so this would put double burden on him. The parallel
operation, however, still has some advantages. II the new system Iails or any error occurs, then
because still we have the old system in operation it can be used Ior as long the problems are
sorted out. The results oI both the systems can also be compared and then looked iI new system
as achieved the speciIied objectives.
Library database management system
40
Correct method of soIution
The correct method oI solution in this case would be to use phased implementation. The data Ior
the library is too precious to be risked by using direct implementation method. The workload is
already encumbering and it cannot be multiplied by using parallel running. The only option that
is leIt is phased implementation, but it has its advantages too. Sometimes there errors that are
common to every table/Iorm in the database, by introducing just one part, the error could be
identiIied and be sorted Ior the rest oI the database. Only aIter it has been insured that the system
is working perIect, and then is the next part implemented.
The librarian would Iirst have to install MicrosoIt oIIice 07 on his computer. This will include a
word, spreadsheet, database (our soItware) and a couple other packages, all oI which are very
useIul. Then the library project Irom the Ilash drive would be copied onto the system. The
database is now ready to be used.
The librarian would Iirst be given the user manual to read careIully and then later on take help
Irom it. Then he would be trained under my supervision. During this session he would be told in
detail about how the system works. II any Iurther inIormation is required the librarian could
contact me on my cell no.
First oI all the record oI all the books oI the library would be entered into the system. This is a
huge job and will take a lot oI time. This time, however, is available. There are months until the
new session would start. All the previous records that are on registers will be preserved in the
cabinets at that time. We would then have a complete record oI all the books. In between this
time iI librarian Iounds anything out oI place in the system, it could be readily corrected. It will
also help him to get used to this system so that he can be comIortable when his job is moved onto
memberships and issuance number.
The sections oI memberships and issuance will be implemented together. When the new session
starts students would come back to renew their memberships. Then he would enter their details
directly into the database. The students won`t be issued membership cards now. But only the
librarian would have the prooI oI their membership. And when they would come to borrow a
book, the librarian could check their membership details.
Library database management system
41
Progrumming code
This code is being written on log in Page so that the button works properly to user name and
password, as written correctly move on to Main Menu or iI written wrong than the message box
will appear "Please reenter your username and password."
Private Sub ommand13lick ()
II Username "Usman" And Password "llibrary" Then
Domd.lose
Domd.OpenForm "Main Menu"
Else
MsgBox "Please reenter your username and password."
End II
End Sub
O This is the programming code Ior the report which is viewed by class.
SELET member.rollno, member.name, member.class, member.contactno,
member.|e-mail|, member.membershipdate
F#OM member
WHE#E (((member.class)|Enter class|))
O#DE# BY member.name;
O This is the programming code Ior report which shows the issuance history oI individual
members
SELET issue.issuanceno, member.rollno, member.name, issue.bookcode,
issue.issuedate, issue.returndate, issue.return
F#OM member IE# JOI issue O member.rollnoissue.rollno
WHE#E (((member.rollno)|Enter roll no|));
O This is the programming code Ior report which shows the books by author name.
SELET books.bookcode, books.booktitle, books.author, books.category, books.price
F#OM books
WHE#E (((books.author)|Enter author name|));
O This is the programming code Ior the report which shows the issuance history oI a book.
Library database management system
42
SELET issue.issuanceno, books.bookcode, books.booktitle, issue.rollno,
issue.issuedate, issue.returndate, issue.return
F#OM books IE# JOI issue O books.bookcode issue.bookcode
WHE#E (((books.bookcode)|enter book code|));
O This is the programming code Ior the report which shows the books by category.
SELET books.bookcode, books.booktitle, books.author, books.category, books.price
F#OM books
WHE#E (((books.category)|Enter category|));
O This is the programming code Ior the report which shows the issued books that have not
been returned
SELET issue.|issuanceno|, issue.|bookcode|, issue.|rollno|, issue.|issuedate|,
issue.|returndate|, issue.|return|
F#OM issue
WHE#E (((issue.|return|)o));
O This is the programming code Ior the report which whows the issued books that have
been returned.
SELET issue.issuanceno, issue.bookcode, issue.rollno, issue.issuedate,
issue.returndate, issue.return
F#OM issue
WHE#E (((issue.return)Yes));
O There is another code used which displays the time on the switchboard and also the log in
page. i.e.
Private Sub FormTimer()
Me!|time| ow()
End Sub
Library database management system
43
Library database management system
44
Test strutegy
The database, beIore it could be implemented should be tested careIully so that any errors that
are leIt or may occur into the processing are kinked out. The data is tested in varieties oI ways. I
tested the data with myselI as a user oI the system who is not an expert and just has the basic
knowledge oI the system. This is also called the user testing. The testing I perIormed on the
database mainly concentrates on the Iollowing:
O Data integrity test
O Stored procedure test
O Type test
O Data size test
O Input item veriIication
O Button testing
Dutu integrity test
Actions: updating/deletion/ Iresh insertion/ display oI new screen/ time bound actions
Once a value undergoes any oI above actions the database should be veriIied Ior the changes
perIormed on related entities i.e. Ioreign key, primary key, and all other dependent entities. For
e.g. when the user issues a book all the reports that are related and the datasheet view at that
books Iorm should show the related changes.
Stored procedure test
Actions: updating/deletion/ Iresh insertion/ display oI new screen/ time bound actions
Every stored procedure is to be tested separately Ior its Iunctionality (based on separate Iunctions
it perIorms). Stored procedure needs to be into items based actions on Iunctions and then each
action item needs to be tested separately as the result oI complete stored procedure. In the case oI
this library management system, the job oI the Iield 'return in the issue/return table is tested and
seen iI the reports that depend on this Iield work properly or not.
Type test
Actions: updating/deletion/ Iresh insertion/ display oI new screen/ time bound actions
This test is perIormed to veriIy that the data types used by DBA are same as expected by the
agreed upon by the developer. OIten the data types chosen by the developers are not the same as
suggested by database administrators especially Ior Iields like:
ontact no. (um./text)
Description (large test)
Library database management system
45
These kinds oI mismatches oIten do not aIIect the Iunctionality and normal execution oI the code
but prove very hectic during updating or addition oI Ieatures to the existing modules. The
rollno, bookcode, the contact no. are all text Iields where as Ior an ordinary user they must be
numbered Iields. The length and input mask has been set Ior them so that the required job could
easily be done.
Dutu size test
Actions: updating/deletion/ Iresh insertion/ display oI new screen/ time bound actions
PerIormance oI data size testing is done only at the Iront end during unit testing, but it is
essential to perIorm it at back end separately. This ensures smooth transition while appending
Iunctionality and integrating modules as during these phases. The data is passed to the system
with direct user interaction and bypassing Iront end validation. When large amounts oI data is
started to be processed, any errors could prove immense Ior the system. So this is careIully
checked Irom the Iorms and as well as Irom the tables.
Input item verificution
Actions: updating/deletion/ Iresh insertion/ display oI new screen/ time bound actions
This is the process oI veriIication oI the input items (text box/#TB/combo box etc) are tested Ior
validation, but these again are to be tested with junk character to conIirm that they do not push
such characters with such databases. OIten they misrepresent or replace with other characters.
The log in page, the time, and other validation rules Ior input text are examples oI it.
uttons testing
Along with this all these types oI tests diIIerent buttons that had been placed on the Iorms and
switchboards were tested and careIully checked is they perIorm the required Iunctions. Also the
error or warning messages that should appear when certain commands were perIormed were also
checked.
Finally when all oI the above were careIully inspected the time Ior the Iinal and most important
tests arrived, which is normal, abnormal and extreme data testing. For this input data Ior all the
tables was separately collected. areIul inspection Ior all the possible input items was done and
was noted down. AIter this painstaking job had been done, the input data was entered to see iI
the expected results had been achieved. onsideration was taken to check iI the system detects
the duplication oI data.
Library database management system
46
NormuI dutu testing
For the normal data testing, I collected the data Irom the librarian`s register. Every time a record
was entered, the computer was supposed to give an 'ALL O signal which is just by not giving
any error message and behaving the way it is supposed to. During this normal testing I took
measures to see iI the objectives about time reduction had been achieved.
Etreme dutu testing
To collect the data to be tested in extreme data testing I simply had a look on the all the Iields in
the database and noted down the data which could Iit Ior this type oI test. In this type oI testing,
the Iields with a set character length were taken into consideration, no warning sound is
supposed to be heard as long the input data is within the range but when it tries to exceed the
limit then beep sounds should be heard. The price Ior the book whose upper limit has been set to
$50 was also checked and the computer was expected to give appropriate error messages when
the limit was transgressed. Dates Ior issuance and return were also a part oI this testing
AbnormuI dutu testing
For this type oI testing the data was collected in a variety oI ways. First oI all I inspected the
membership Iorms under the supervision oI the librarian. He told me about some oI the Iields
that had been wrongly Iilled in. I noted them down and applied them on the membership table`s
Iield to see iI this database points out the errors. Then he told me about other insensible data that
he sometimes encounters. The range oI data that was tested was very wide. The character type
test that had been mentioned above were a part oI this testing. Dates, primary Iields and
parameter values Ior the reports were tested. To point out such errors the computer is supposed
to give both an error message and beep or warning sound.
Other ussessments
When the normal data testing had been going on I took special measures to see iI some oI the
objectives that were set out in the beginning oI the project had been achieved or not. The time
reduction objective was checked with the help oI librarian which was expected to be achieved.
For some part oI the normal testing librarian was made to enter the data and perIorm Iunctions
Ior some his training and my observation iI the system was user-Iriendly and layout was easy to
use or not.
For abnormal and extreme data testing I again included some measures to see iI objectives
related to this Iield had been met or not. When data was wrongly or mistakenly entered, it was
seen iI it was easier Ior the librarian to edit it. Human errors which are a big drawback oI manual
systems were also investigated Ior the database. Most oI them are supposed to be pointed out.
Finally the last thing that included the test strategy was to see iI validation checks had been
working properly and one oI its Iunctions was to cut out the duplication. This I supposed to be
pointed out with an error message in the primary Iields iI duplication occurs.
Library database management system
47
Test ResuIts
NormuI dutu testing
O Books table
books
book_code book_t|t|e author category pr|ce
12231 Culde Lo ulLlmaLe success Pasan larooql lslamlyaL $2200
12309 PlsLory and CulLure of aklsLan Puma naaz seLhl hlsLory $700
12324 sLar anLhony asLrology $1200
23S67 llfe of ropheL(pbuh) farkhanda noor lslamlyaL $330
23948 splder naslm buLL compuLer $100
32147 ars of Lhe orld slr syed ahmed khan hlsLory $230
38974 bangedara lqbal urdu $100
S4707 compuLer sLudles an lnLroducLory course chrls lecek compuLer $300
61748 lsk managemenL Lherese vaughan accounLs $1000
81928 lncrease your lC P fayyaz g knoledge $1030
91328 human anaLomy klla[n Shah 8lology $2000
98230 harmful lnLenL adam gllchrlsL engllsh $4000
Library database management system
48
O Members table
eber
ro||_no nae c|ass contact_no ea|| Mebersh|p
date
10S39600 Dsman Ahmed C2 A 03312214039 usman_436[llvecom 12/14/2010
1204618S mAbdullah CCA 03112263311 gunzzz_123[gmallcom 12/21/2010
12121212 aseer MusLafa CC8 02349174761 yaseermusLafa[llvecom 1/1/2011
12908409 @alha lqbal 10 f 03312936203 Lalhalqbal34[yahoocom 12/30/2010
12949300 @alha Chaudhry C2 A 03342817384 llLLle_rascal[hoLmallcouk 12/14/2010
13021628 Dsama Slddlque 10 u 03339269989 usama _pa[ama[yahoocom 11/16/2010
13048242 8llal Zubalr 10 ! 03231026493 blllu_barbar[hoLmallcom 11/23/2010
13812312 Ahsan ehman C2 8 03112943620 devll_rocker[ohoLmallcouk 11/21/2010
2012S4S8 ousaf noor C2 A 03321237324 seeLy_LeeLy[hoLmallcom 1/13/2011
314S8200 Ahsan All 9 8 03321309628 badshah_ahsan[hoLmallcom 12/7/2010
O Issue table
|ssue
|ssuance_no book_code ro||_no |ssue_date return_date return
1 12324 10339600 11/1/2010 11/10/2010 es
3 23367 10339600 11/3/2010 11/13/2010 es
4 12309 13812312 11/9/2010 11/21/2010 es
S 98230 20123438 11/13/2010 11/23/2010 es
6 38974 12046183 11/13/2010 12/9/2010 es
7 81928 12949300 11/23/2010 12/3/2010 es
8 12324 20123438 12/1/2010 12/10/2010 no
9 32147 31438200 12/14/2010 12/24/2010 no
10 61748 10339600 12/14/2010 1/17/2011 es
11 98230 12121212 11/18/2010 12/1/2010 no
All this data was entered in the above tables Ior normal testing and no error message or
warning was given by the computer.
Library database management system
49
AbnormuI dutu testing
O Book`s table
Sr.
no
FieId
nome
Dofo
enfered
Error messoge or observofion Pemork
1
Bookcode IL Primary key cannot contain a null
value
Primary key to be
assigned
Z
Bookcode Alphabets 'bing sound heard Only digits are
allowed
3
Price Any number
e.g. 4
onverted to currency as assigned in
data type
$4.00
4
Price Alphabets On save 'The value you entered isn`t
valid Ior this Iield
Only digits are
allowed
O Members table
Sr.no FieId nome Dofo enfered Error messoge or
observofion
Pemorks
1
#ollno il Primary key cannot contain
a null value
Primary key to
be assigned
Z
#ollno Alphabets 'bing sound heard Only digits are
allowed
3
ontactno Alphabets 'bing sound heard Only digits are
allowed
4
Membership
date
Alphabets or wrong
dates e.ge
121/23/1289
On save 'The value you
entered isn`t valid Ior this
Iield
Only date type
Iormat is
allowed
Library database management system
50
O Issue table
Sr.no FieId
nome
Dofo enfered Error messoge or
observofion
Pemorks
1
Issuanceno Any character sound heard Irom computer It is an auto number
Iield. o need to type
anything
Z
Bookcode Anything besides
data in drop down
box
You cannot add or change a
record because a related
record is required in table
'books
Only data Irom the
drop down box can be
selected/typed
3
#ollno Anything besides
data in drop down
box
You cannot add or change a
record because a related
record is required in table
'member
Only data Irom the
drop down box can be
selected/typed
4
issuedate Alphabets or
wrong dates e.ge
121/23/1289
On save 'The value you
entered isn`t valid Ior this
Iield
Only date type Iormat
is allowed i.e.
mm/dd/yyyy
returndate Alphabets or
wrong dates e.ge
121/23/1289
On save 'The value you
entered isn`t valid Ior this
Iield
Only date type Iormat
is allowed i.e
mm/dd/yyy
Library database management system
51
Etreme dutu testing
O Book`s table
Sr,no FieId
nume
Dutu
entered
Error messuge or observution Remurks
1
Bookcode More than 5
digits typed
Warning sound heard Only 5 digits
can be typed
Z
Booktitle More than 50
alphabets
typed
Warning sound heard Only 5
alphabets can
be typed
3
Author More than 30
alphabets
typed
Warning sound heard Only 30
alphabets can
be typed
4
ategory More than 15
alphabets
typed
Warning sound heard Only 15
alphabets can
be typed
Price More than 50 'One or more values are prohibited by
the validation rule '50 set Ior
'books.price. enter a value that the
expression Ior this Iield can accept
Price should
be less than $
50
O Member`s table
Sr,no FieId nome Dofo enfered Error messoge or
observofion
Pemorks
1
#ollno More than 8
digits typed
Warning sound heard Only 8 digits can be
typed
Z
ame More than 30
digits typed
Warning sound heard Only 30 digits can
be typed
3
lass More than 4
digits typed
Warning sound heard Only 4 digits can be
typed
4
ontactno More than 11
digits typed
Warning sound heard Only 11 digits can
be typed
e-mail More than 40
digits typed
Warning sound heard Only 40 digits can
be typed
Memberhipdate 2/32/11 The value you entered isn`t
valid Ior this Iield
Days can`t be more
31in a month
Library database management system
52
O Issue table
Sr,no FieId
nume
Dutu
entered
Error messuge or
observution
Remurks
1
Issuedate 2/32/11 The value you entered isn`t
valid Ior this Iield
Days can`t be more
31in a month
Z
#eturndate 2/32/11 The value you entered isn`t
valid Ior this Iield
Days can`t be more
31in a month
Library database management system
53
User documentution
A user manual about the project is also made in which the librarian would be explained how to
run the project and how to use it on the computer system
First oI all the computer system should meet the soItware and hardware requirements Ior the
system. These requirements have been explained earlier. AIter that the soItware needs to be
installed. For that Iollowing steps should be taken:
O Insert the D #OM into the D #OM drive
O Open the D drive in my computer
O opy the program Irom the D drive
O Paste it where ever you want the soItware to be.
ow we will see how to run the program. We will see each Iunction in detail.
User has to click the icon oI the database. A password acquiring window will open
which would ask the user Ior the authentic password assigned to the database Ior security
reasons. The Iorm resembles the Iollowing window:
Library database management system
54
The security warning option bar on the top oI the login page is a built in Ieature oI this soItware
that helps protect your computer against any macros introduced by a hacker to destroy the
database system. It won`t allow the user to access the system as long as all the macros have been
enabled. This is done simply by clicking on the option button . The Iollowing
window will appear. The 'enable this content option is selected and then click on O. The
system is now ready to Iunction.
The sign in button is used to enter the into the database system. II an
incorrect username and password is written or the text boxes aren`t Iilled and the sign in button
is clicked then the database will show an error oI the Iollowing sort:
Library database management system
55
When the user will enter the correct password the main Iorm oI the database will open. The
correct username and password Ior this project are 'usman and 'library respectively. The
password can be changed but a skilled person is required to do that. It will be adjusted to the
need oI librarian when the system will be implemented.
The date also appears on this Iorm. This date resemebles to that oI the date oI the users
computer. To change this date, the date oI computer will have to be changed.
Main Iorm oI the database is the gateway to whole oI the designed soItware. To reach any
portion oI the database, the user will Iind the main Iorm as the key Iorm Irom where the user
can go anywhere. The main Iorm is as Iollows:
It entirely depends upon the user to click any button. The commands on the button make it
simply clear about which Iorm will open aIter clicking any particular button. The sign out
button at the bottom right corner oI the page will take the librarian back to the log in so that
no one else can access this page.
The option oI books in this menu will lead to a Iorm that contains all possible operations that
librarian perIorms in relation to the books. The Iollowing Iorm appears:
Library database management system
56
The choices oI records are in Iront oI the user and desirable Iorm can be accessed by clicking
the respective button. II the librarian desires to enter the a new book then he will click the
button 'enter new record and Iind himselI in Iront oI another opened Iorm which will be oI
books resembling the Iorm as Iollows:
Library database management system
57
The three buttons shown do the Iollowing job:
This button saves the record aIter a new complete record has been entered. II the book
code contains a null value than and this button is pressed, the Iollowing error message
appears.
This button will remove all the details that have been entered. And an empty Iorm will
again appear.
Library database management system
58
This button would lead back to the books switchboard.
This grid
could be
used to issue
this book as
soon as this
book is
entered.
The navigation bar at the bottom oI the page could be used to navigate through the records.
Since this Iorm has been opened in add mode so only the records that have been entered just
now could be navigated through.
Library database management system
59
The second button on the books switchboard would lead to the same Iorm with some editing
done on it. This is the Iorm.
This Iorm has been opened in edit mode and could be used to edit data oI books. To select a
particular record the combo box is used.
The combo box on the top would open a drop down box as shown. It would show the book code
and the name oI the book. The required book could be chosen Irom this drop down menu.
The buttons here do the same job as they did in the previous Iorm. The delete button here would
delete a record aIter the Iollowing message appears.
Library database management system
60
The grid could
used to show iI
this book has
been lent or not.
It can also show
all the issuing
inIormation. II
this books needs
to be lent the
details can be entered here as well as in the issuing Iorm which will be shown later.
This navigation pane on the bottom oI the page can be used to go to the next or previous record.
The search box can be used to input any inIormation that needs to be retrieved e.g. one can enter
the price oI the book and a book pertaining to that cost will appear upIront.
Library database management system
61
The other Iour buttons on the books switchboard are Ior the reports. All these are as Iollows.
All books
This above report shows all the books that are in the library. To print this page ctrlp could be
pressed and the report will be printed. The x button on the corner oI the report will close the
report and this lead back to book switchboard.
Library database management system
62
O Book`s issuance history
This window asks the book code. When this is entered a report
appears that tells about the issuance history oI a particular book.
This report shows that this book was issued on such and such date and to the stated student. The
due date Ior this is 14
th
oI Jan. and it has not yet been returned.
Library database management system
63
Books by author name
This would open the books pertaining to a particular author.
Library database management system
64
Books by category
This would open a report that would contain all the books relating to a particular category
O The BA TO MAI MEU button will lead back to the main Iorm.
Library database management system
65
The next button on the main Iorm is the member`s button. The Iollowing page will appear when
it is clicked.
Members
This screen contains Iive buttons all oI which do their respective Iunctions.
Library database management system
66
O The Iirst button 'ETE# EW MEMBE# opens a Iorm in add mode and the screen
just like the book record appears. This is the Iorm:
The three buttons shown do the Iollowing job:
This button saves the record aIter a new complete record has been entered. II the
book code contains a null value than and this button is pressed, the Iollowing error
message appears.
This button deletes the record entered.
This button would lead back to the books switchboard.
Library database management system
67
This grid could be used to issue this book as soon as this book is entered.
O The second button 'EDIT MEMBE#`S DATA opens the Iorm in edit mode. This Iorm
also contains a combo box as in edit mode in books report. This works exactly the same
way. The buttons and the grid also hold the same Iunction. This is the Iorm:
Library database management system
68
O The third button 'ALL MEMBE#S #EPO#T will open a report that contains the
inIormation oI all the students who are member oI the library. This and all the other
reports could be printed in the same manner.
Library database management system
69
O The Iourth button 'MEMB#ESHIP BY LASS opens the Iollowing window. The name
oI any class can be entered here and then the
report oI all the students who belong to a
particular class will appear.
This is the report:
O The IiIth button 'MEMBE#S ISSUAE
HISTO#Y opens the Iollowing window: the
roll no. oI any student can be entered here and
the issuance history oI that student will appear.
This report is the same as the issuance history oI
a book except that the criterion there was Ior a
book and here it is Ior the members.
Library database management system
70
This is the report:
O The last button would bring the user back to main menu.
Library database management system
71
Issue a book
The third button on the main menu is issue a book. On click the Iollowing Iorm will appear.
Here the book code and the roll no are chosen Irom the drop down box. II the roll no or the
book code is something else than that stored in the database than the Iollowing error message
will appear: Similar
message will appear when roll no is chosen something else than that in the drop down box.
A calendar would appear iI selected on the issue and return date.
This calendar could be used to select the date Ior both issue and
return. Anything entered that is not the Iormat oI a date will not be
accepted.
Library database management system
72
Return a book
The Iourth button on the main menu is to return a book. When clicked; the Iollowing Iorm
will appear:
the
combo box would drop down a list oI issuance number along with the roll no and the book
code. #equired issuance number is selected and when the record appears: the book could be
returned by clicking the empty box in Iront oI the Iield 'return. The buttons do the same job
here as they do on other Iorms.
Library database management system
73
Issuance history
The Iollowing switchboard when the issuance history is selected:
All oI these are the reports. Their purpose is as Iollows:
O The Iirst button 'issued books would open up a report which contains the inIormation about
all the books that have been issued and not yet return. This way the librarian could easily Iind
the deIaulter.
Library database management system
74
O The second button 'returned books shows all the issued books that have been returned. This
could be used Ior statistical inIormation e.g. how many books were lent and returned a
particular month?
Library database management system
75
O The third button 'books issuance history opens up the same report as the button by the same
name in the books switchboard opens. Since it I related to both the switchboards so the
button has been displayed twice.
O The third button 'member`s issuance history opens up the same report as the button by the
same name in the members switchboard opens. Since it I related to both the switchboards so
the button has been displayed twice.
O The 'back to main menu button opens the main menu.
Exit
The exit button closes the database.
This button that appears on the bottom right corner oI the page would log the
user out and the log in page will appear. This button is hyperlinked so that the librarian would
know that it is simply not text.
Library database management system
76
TechnicuI documentution
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: books Page: 1
Properties
DateCreated: 12/14/2010 10:21:03 AN Defaltview: 2
DisplayviewsOnSarePoint 1 FilterOnLoad: False
CU!D: {gid {3DEC1E2CB2FE HideNewField: False
47F1AA0B
LastUpdated: 1/3/2011 10:17:13 PN NameNap: Long binary data
OrderByOn: False OrderByOnLoad: 're
Orientation: LefttoRigt RecordCont: 11
'otalsRow: False Updatable: 're
olumns
Name 'ype Size
book_code 'ext S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {33DB7AS3S3S6484D823B2F1A8SBDF322}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 0
Reqired: False
SorceField: book_code
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: False
book_title 'ext S0
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 331S
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {8C3633C333DE4A80BA188624F402CC30}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: book_title
Sorce'able: books
Library database management system
77
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: books Page: 2
'extAlign: Ceneral
UnicodeCompression: 're
ator 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1380
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {17E0B11F6SF64B3EAE3B00A2EAS8E13F}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: ator
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
category 'ext 1S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 184S
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {313CD0BAEDBA41F33E32D01D373DB332}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SorceField: category
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
price Crrency 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 34S
DataUpdatable: False
DecimalPlaces: Ato
Library database management system
78
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: books Page: 3
Format: $#,##0.00,($#,##0.00)
CU!D: {gid {2SC643B06F4A4624BF0AC74DDBE820C3}}
OrdinalPosition: 4
Reqired: False
SorceField: price
Sorce'able: books
'extAlign: Ceneral
validationRle: <S0
%elationships
booksissue
books issue
book_code 1 C book_code
Attribtes: Enforced, Cascade Updates, Cascade Deletes
Relationsip'ype: One'oNany
'able !ndexes
Name Nmber of Fields
PrimaryKey 1
Clstered: False
DistinctCont: 6
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
book_code Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
79
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: isse Page: 4
Properties
DateCreated: 12/14/2010 10:26:2S AN Defaltview: 2
DisplayviewsOnSarePoint 1 FilterOnLoad: False
CU!D: {gid {763F4C3EE7214F37 HideNewField: False
3C80F37CFAB44EFD}}
LastUpdated: 12/28/2010 12:00:43 PN NameNap: Long binary data
OrderByOn: False OrderByOnLoad: 're
Orientation: LefttoRigt RecordCont: 8
'otalsRow: False Updatable: 're
olumns
Name 'ype Size
issance_no Long !nteger 4
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Ato!ncrement
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: 1
ColmnWidt: Defalt
DataUpdatable: False
CU!D: {gid {EB8CE37F4S0S43ED8S6A33DE43030AF4}}
OrdinalPosition: 0
Reqired: False
SorceField: issance_no
Sorce'able: isse
'extAlign: Ceneral
book_code 'ext S
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: False
DisplayControl: Combo Box
CU!D: {gid {073E1C3423ED41S43B043BF63EF33C70}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
Library database management system
80
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: isse Page: S
ListWidt: 1440twip
OrdinalPosition: 1
Reqired: False
RowSorce: SELEC' |books].|book_code] FRON books,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: book_code
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
roll_no 'ext 3
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: False
DisplayControl: Combo Box
CU!D: {gid {C640FSC26S634D33B07A34263A3E8ASB}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 2
Reqired: False
RowSorce: SELEC' |member].|roll_no] FRON member,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: roll_no
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
isse_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
CU!D: {gid {8E788CEE46SA4B60AE3E1FA31B7036E0}}
!NENode: 0
Library database management system
81
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: isse Page: 6
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SowDatePicker: For dates
SorceField: isse_date
Sorce'able: isse
'extAlign: Ceneral
retrn_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
CU!D: {gid {3427SB123F3S4B47B1C3D0B33A7EF2A8}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SowDatePicker: For dates
SorceField: retrn_date
Sorce'able: isse
'extAlign: Ceneral
retrn Yes/No 1
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1440
DataUpdatable: False
DisplayControl: 106
Format: Yes/No
CU!D: {gid {8404863S3EF84SDBA20F230BCB3A1E13}}
OrdinalPosition: S
Reqired: False
SorceField: retrn
Sorce'able: isse
'extAlign: Ceneral
%elationships
Library database management system
82
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: isse Page: 7
booksissue
books issue
book_code 1 C book_code
Attribtes: Enforced, Cascade Updates, Cascade Deletes
Relationsip'ype: One'oNany
memberissue
member issue
roll_no 1 C roll_no
Attribtes: Enforced, Cascade Updates, Cascade Deletes
Relationsip'ype: One'oNany
'able !ndexes
Name Nmber of Fields
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Library database management system
83
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: isse Page: 8
Uniqe: 're
Fields:
issance_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
84
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: member Page: 3
Properties
DateCreated: 12/14/2010 10:16:2S AN Defaltview: 2
DisplayviewsOnSarePoint 1 FilterOnLoad: False
CU!D: {gid {8SS11310677442E6 HideNewField: False
37761C7ED3DA2SE8}}
LastUpdated: 1/3/2011 10:37:22 PN NameNap: Long binary data
OrderByOn: False OrderByOnLoad: 're
Orientation: LefttoRigt RecordCont: 10
'otalsRow: False Updatable: 're
olumns
Name 'ype Size
roll_no 'ext 3
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {CD22E1CE760342B63032428131028C4D}}
!NENode: 0
!NESentenceNode: 3
!nptNask: 000000\00,,_
OrdinalPosition: 0
Reqired: False
SorceField: roll_no
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: False
name 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 20SS
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {643FB8SA684C4C2AA30A3E3CB1341730}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: name
Library database management system
85
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: member Page: 10
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
class 'ext 4
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {BF637A6S773E48BFA7E176E624A6A36B}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: class
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
contact_no 'ext 11
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {SF3A3FC343084328B1BDC84D26DF4814}}
!NENode: 0
!NESentenceNode: 3
!nptNask: 3333\3333333,,_
OrdinalPosition: 3
Reqired: False
SorceField: contact_no
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
email 'ext 40
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 2880
Library database management system
86
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: member Page: 11
DataUpdatable: False
DisplayControl: 'ext Box
CU!D: {gid {3SFCA3200F2C4DCEB3A7683814SE2EE7}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SorceField: email
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
membersip_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 148S
DataUpdatable: False
CU!D: {gid {041BA8AD436D4C1C8AF6E843S3SEDD3F}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: S
Reqired: False
SowDatePicker: For dates
SorceField: membersip_date
Sorce'able: member
'extAlign: Ceneral
%elationships
memberissue
member issue
roll_no 1 C roll_no
Attribtes: Enforced, Cascade Updates, Cascade Deletes
Relationsip'ype: One'oNany
'able !ndexes
Name Nmber of Fields
PrimaryKey 1
Clstered: False
DistinctCont: 1
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Library database management system
87
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: member Page: 12
Reqired: 're
Uniqe: 're
Fields:
roll_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
88
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: Switcboard !tems Page: 13
Properties
DateCreated: 12/14/2010 10:11:38 PN CU!D: {gid {DS3E70D6B3C6
4180B87DSCS8E1SB6B62}}
LastUpdated: 12/14/2010 10:11:38 PN RecordCont: 28
Updatable: 're
olumns
Name 'ype Size
Switcboard!D Long !nteger 4
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Netral
DataUpdatable: False
CU!D: {gid {FF311D02330B444D8427E0DS78D1668B}}
OrdinalPosition: 0
Reqired: False
SorceField: Switcboard!D
Sorce'able: Switcboard !tems
!temNmber !nteger 2
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Netral
DataUpdatable: False
CU!D: {gid {1316S62B184F46F4883A2ACDB630S4CB}}
OrdinalPosition: 1
Reqired: False
SorceField: !temNmber
Sorce'able: Switcboard !tems
!tem'ext 'ext 2SS
AllowZeroLengt: False
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
DataUpdatable: False
CU!D: {gid {0S0F1DS3F33B4630BSCDC6S232BAF7D3}}
OrdinalPosition: 2
Reqired: False
SorceField: !tem'ext
Sorce'able: Switcboard !tems
Command !nteger 2
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size
CollatingOrder: Netral
DataUpdatable: False
CU!D: {gid {3C0A13FF821A4677ABE30C46383C1341}}
OrdinalPosition: 3
Library database management system
89
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
'able: Switcboard !tems Page: 14
Reqired: False
SorceField: Command
Sorce'able: Switcboard !tems
Argment 'ext 2SS
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt
CollatingOrder: Ceneral
DataUpdatable: False
CU!D: {gid {B0C1SD162826430136SF02BB333FE12F}}
OrdinalPosition: 4
Reqired: False
SorceField: Argment
Sorce'able: Switcboard !tems
'able !ndexes
Name Nmber of Fields
PrimaryKey 2
Clstered: False
DistinctCont: 28
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
Switcboard!D Ascending
!temNmber Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
90
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: ator name Page: 1S
Properties
DateCreated: 12/14/2010 8:S3:28 PN Defaltview: 2
DisplayviewsOnSarePoint 1 DOL: Long binary data
FilterOnLoad: False CU!D: {gid {C3BFA7C10B8S
41DB33D826B03C30A1SS}}
HideNewField: False LastUpdated: 12/14/2010 10:28:02 PN
NaxRecords: 0 NameNap: Long binary data
ODBC'imeot: 60 OrderByOn: False
OrderByOnLoad: 're Orientation: LefttoRigt
RecordLocks: No Locks RecordsAffected: 0
Recordset'ype: Dynaset RetrnsRecords: 're
'otalsRow: False 'ype: 0
Updatable: 're
&$
SELEC' books.book_code, books.book_title, books.ator, books.category, books.price
FRON books
WHERE (((books.ator)=|Enter ator name])),
$uery Parameters
Name 'ype
|Enter ator name] 'ext
olumns
Name 'ype Size
book_code 'ext S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {33DB7AS3S3S6484D823B2F1A8SBDF322}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 0
Reqired: False
SorceField: book_code
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: False
book_title 'ext S0
Aggregate'ype: 1
AllowZeroLengt: 're
Library database management system
91
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: ator name Page: 16
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 331S
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {8C3633C333DE4A80BA188624F402CC30}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: book_title
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
ator 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1380
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {17E0B11F6SF64B3EAE3B00A2EAS8E13F}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: ator
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
category 'ext 1S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 184S
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {313CD0BAEDBA41F33E32D01D373DB332}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SorceField: category
Library database management system
92
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: ator name Page: 17
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
price Crrency 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 34S
DataUpdatable: 're
DecimalPlaces: Ato
Format: $#,##0.00,($#,##0.00)
CU!D: {gid {2SC643B06F4A4624BF0AC74DDBE820C3}}
OrdinalPosition: 4
Reqired: False
SorceField: price
Sorce'able: books
'extAlign: Ceneral
validationRle: <S0
'able !ndexes
Name Nmber of Fields
PrimaryKey 1
Clstered: False
DistinctCont: 6
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
book_code Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
93
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 18
Properties
DateCreated: 12/14/2010 3:03:36 PN Defaltview: 2
DOL: Long binary data FilterOnLoad: False
CU!D: {gid {A3B6F6SF8FCS LastUpdated: 12/14/2010 10:23:41 PN
436SA03S
NaxRecords: 0 ODBC'imeot: 60
OrderByOn: False OrderByOnLoad: 're
Orientation: LefttoRigt RecordLocks: No Locks
RecordsAffected: 0 Recordset'ype: Dynaset
RetrnsRecords: 're 'otalsRow: False
'ype: 0 Updatable: 're
&$
SELEC' isse.issance_no, books.book_code, books.book_title, isse.roll_no, isse.isse_date,
isse.retrn_date, isse.retrn
FRON books !NNER ]O!N isse ON books.book_code=isse.book_code
WHERE (((books.book_code)=|enter book code])),
$uery Parameters
Name 'ype
|enter book code] 'ext
olumns
Name 'ype Size
issance_no Long !nteger 4
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Ato!ncrement, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: 1
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {EB8CE37F4S0S43ED8S6A33DE43030AF4}}
OrdinalPosition: 0
Reqired: False
SorceField: issance_no
Sorce'able: isse
'extAlign: Ceneral
book_code 'ext S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
Library database management system
94
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 13
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {33DB7AS3S3S6484D823B2F1A8SBDF322}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: book_code
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: False
book_title 'ext S0
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 331S
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {8C3633C333DE4A80BA188624F402CC30}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: book_title
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
roll_no 'ext 3
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {C640FSC26S634D33B07A34263A3E8ASB}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
Library database management system
95
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 20
ListWidt: 1440twip
OrdinalPosition: 3
Reqired: False
RowSorce: SELEC' |member].|roll_no] FRON member,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: roll_no
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
isse_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {8E788CEE46SA4B60AE3E1FA31B7036E0}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SowDatePicker: For dates
SorceField: isse_date
Sorce'able: isse
'extAlign: Ceneral
retrn_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {3427SB123F3S4B47B1C3D0B33A7EF2A8}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: S
Reqired: False
SowDatePicker: For dates
SorceField: retrn_date
Sorce'able: isse
'extAlign: Ceneral
retrn Yes/No 1
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
Library database management system
96
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 21
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1440
DataUpdatable: 're
DisplayControl: 106
Format: Yes/No
CU!D: {gid {8404863S3EF84SDBA20F230BCB3A1E13}}
OrdinalPosition: 6
Reqired: False
SorceField: retrn
Sorce'able: isse
'extAlign: Ceneral
'able !ndexes
Name Nmber of Fields
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 6
Library database management system
97
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 22
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
book_code Ascending
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
98
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: books issance istory Page: 23
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
99
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: category Page: 24
Properties
DateCreated: 12/14/2010 3:01:22 PN Defaltview: 2
DisplayviewsOnSarePoint 1 DOL: Long binary data
FilterOnLoad: False CU!D: {gid {DBA24S1433D1
437FAE470DF243422E12}}
HideNewField: False LastUpdated: 12/14/2010 3:22:02 PN
NaxRecords: 0 NameNap: Long binary data
ODBC'imeot: 60 OrderByOn: False
OrderByOnLoad: 're Orientation: LefttoRigt
RecordLocks: No Locks RecordsAffected: 0
Recordset'ype: Dynaset RetrnsRecords: 're
'otalsRow: False 'ype: 0
Updatable: 're
&$
SELEC' books.book_code, books.book_title, books.ator, books.category, books.price
FRON books
WHERE (((books.category)=|Enter category])),
$uery Parameters
Name 'ype
|Enter category] 'ext
olumns
Name 'ype Size
book_code 'ext S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {33DB7AS3S3S6484D823B2F1A8SBDF322}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 0
Reqired: False
SorceField: book_code
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: False
book_title 'ext S0
Aggregate'ype: 1
AllowZeroLengt: 're
Library database management system
100
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: category Page: 2S
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 331S
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {8C3633C333DE4A80BA188624F402CC30}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: book_title
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
ator 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1380
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {17E0B11F6SF64B3EAE3B00A2EAS8E13F}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: ator
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
category 'ext 1S
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 184S
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {313CD0BAEDBA41F33E32D01D373DB332}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SorceField: category
Library database management system
101
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: category Page: 26
Sorce'able: books
'extAlign: Ceneral
UnicodeCompression: 're
price Crrency 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 34S
DataUpdatable: 're
DecimalPlaces: Ato
Format: $#,##0.00,($#,##0.00)
CU!D: {gid {2SC643B06F4A4624BF0AC74DDBE820C3}}
OrdinalPosition: 4
Reqired: False
SorceField: price
Sorce'able: books
'extAlign: Ceneral
validationRle: <S0
'able !ndexes
Name Nmber of Fields
PrimaryKey 1
Clstered: False
DistinctCont: 6
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
book_code Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
102
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: class Page: 27
Properties
DateCreated: 12/14/2010 3:10:4S PN Defaltview: 2
DisplayviewsOnSarePoint 1 DOL: Long binary data
FilterOnLoad: False CU!D: {gid {C333D6ED4377
467EBDCS
HideNewField: False LastUpdated: 12/14/2010 3:18:42 PN
NaxRecords: 0 NameNap: Long binary data
ODBC'imeot: 60 OrderByOn: False
OrderByOnLoad: 're Orientation: LefttoRigt
RecordLocks: No Locks RecordsAffected: 0
Recordset'ype: Dynaset RetrnsRecords: 're
'otalsRow: False 'ype: 0
Updatable: 're
&$
SELEC' member.roll_no, member.name, member.class, member.contact_no, member.|email],
member.membersip_date
FRON member
WHERE (((member.class)=|Enter class]))
ORDER BY member.name,
$uery Parameters
Name 'ype
|Enter class] 'ext
olumns
Name 'ype Size
roll_no 'ext 3
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {CD22E1CE760342B63032428131028C4D}}
!NENode: 0
!NESentenceNode: 3
!nptNask: 000000\00,,_
OrdinalPosition: 0
Reqired: False
SorceField: roll_no
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: False
Library database management system
103
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: class Page: 28
name 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 20SS
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {643FB8SA684C4C2AA30A3E3CB1341730}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 1
Reqired: False
SorceField: name
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
class 'ext 4
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {BF637A6S773E48BFA7E176E624A6A36B}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: class
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
contact_no 'ext 11
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {SF3A3FC343084328B1BDC84D26DF4814}}
!NENode: 0
!NESentenceNode: 3
Library database management system
104
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: class Page: 23
!nptNask: 3333\3333333,,_
OrdinalPosition: 3
Reqired: False
SorceField: contact_no
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
email 'ext 40
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 2880
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {3SFCA3200F2C4DCEB3A7683814SE2EE7}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SorceField: email
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
membersip_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 148S
DataUpdatable: 're
CU!D: {gid {041BA8AD436D4C1C8AF6E843S3SEDD3F}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: S
Reqired: False
SowDatePicker: For dates
SorceField: membersip_date
Sorce'able: member
'extAlign: Ceneral
'able !ndexes
Name Nmber of Fields
PrimaryKey 1
Clstered: False
DistinctCont: 1
Library database management system
105
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: class Page: 30
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
roll_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
106
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: issed Page: 31
Properties
DateCreated: 12/14/2010 3:24:24 PN Defaltview: 2
DisplayviewsOnSarePoint 1 DOL: Long binary data
FilterOnLoad: False CU!D: {gid {F31617A3S20E431E
A7BFS8BDAA033F04}}
HideNewField: False LastUpdated: 12/14/2010 3:27:12 PN
NaxRecords: 0 NameNap: Long binary data
ODBC'imeot: 60 OrderByOn: False
OrderByOnLoad: 're Orientation: LefttoRigt
RecordLocks: No Locks RecordsAffected: 0
Recordset'ype: Dynaset RetrnsRecords: 're
'otalsRow: False 'ype: 0
Updatable: 're
&$
SELEC' isse.|issance_no], isse.|book_code], isse.|roll_no], isse.|isse_date], isse.|retrn_date],
isse.|retrn]
FRON isse
WHERE (((isse.|retrn])=No)),
olumns
Name 'ype Size
issance_no Long !nteger 4
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Ato!ncrement, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: 1
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {EB8CE37F4S0S43ED8S6A33DE43030AF4}}
OrdinalPosition: 0
Reqired: False
SorceField: issance_no
Sorce'able: isse
'extAlign: Ceneral
book_code 'ext S
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
Library database management system
107
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: issed Page: 32
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {073E1C3423ED41S43B043BF63EF33C70}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 1
Reqired: False
RowSorce: SELEC' |books].|book_code] FRON books,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: book_code
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
roll_no 'ext 3
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {C640FSC26S634D33B07A34263A3E8ASB}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 2
Reqired: False
RowSorce: SELEC' |member].|roll_no] FRON member,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: roll_no
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
isse_date Date/'ime 8
Aggregate'ype: 1
Library database management system
108
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: issed Page: 33
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {8E788CEE46SA4B60AE3E1FA31B7036E0}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SowDatePicker: For dates
SorceField: isse_date
Sorce'able: isse
'extAlign: Ceneral
retrn_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {3427SB123F3S4B47B1C3D0B33A7EF2A8}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SowDatePicker: For dates
SorceField: retrn_date
Sorce'able: isse
'extAlign: Ceneral
retrn Yes/No 1
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1440
DataUpdatable: 're
DisplayControl: 106
Format: Yes/No
CU!D: {gid {8404863S3EF84SDBA20F230BCB3A1E13}}
OrdinalPosition: S
Reqired: False
SorceField: retrn
Sorce'able: isse
'extAlign: Ceneral
Library database management system
109
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: issed Page: 34
'able !ndexes
Name Nmber of Fields
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
110
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 3S
Properties
DateCreated: 12/14/2010 3:13:33 PN Defaltview: 2
DOL: Long binary data FilterOnLoad: False
CU!D: {gid {484FC842DC6D LastUpdated: 12/14/2010 10:23:2S PN
47D7AB1B67BSDA28762C}}
NaxRecords: 0 ODBC'imeot: 60
OrderByOn: False OrderByOnLoad: 're
Orientation: LefttoRigt RecordLocks: No Locks
RecordsAffected: 0 Recordset'ype: Dynaset
RetrnsRecords: 're 'otalsRow: False
'ype: 0 Updatable: 're
&$
SELEC' isse.issance_no, member.roll_no, member.name, isse.book_code, isse.isse_date,
isse.retrn_date, isse.retrn
FRON member !NNER ]O!N isse ON member.roll_no=isse.roll_no
WHERE (((member.roll_no)=|Enter roll no])),
$uery Parameters
Name 'ype
|Enter roll no] 'ext
olumns
Name 'ype Size
issance_no Long !nteger 4
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Ato!ncrement, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: 1
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {EB8CE37F4S0S43ED8S6A33DE43030AF4}}
OrdinalPosition: 0
Reqired: False
SorceField: issance_no
Sorce'able: isse
'extAlign: Ceneral
roll_no 'ext 3
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
Library database management system
111
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 36
ColmnWidt: Defalt
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {CD22E1CE760342B63032428131028C4D}}
!NENode: 0
!NESentenceNode: 3
!nptNask: 000000\00,,_
OrdinalPosition: 1
Reqired: False
SorceField: roll_no
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: False
name 'ext 30
Aggregate'ype: 1
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 20SS
DataUpdatable: 're
DisplayControl: 'ext Box
CU!D: {gid {643FB8SA684C4C2AA30A3E3CB1341730}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 2
Reqired: False
SorceField: name
Sorce'able: member
'extAlign: Ceneral
UnicodeCompression: 're
book_code 'ext S
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {073E1C3423ED41S43B043BF63EF33C70}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
Library database management system
112
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 37
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 3
Reqired: False
RowSorce: SELEC' |books].|book_code] FRON books,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: book_code
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
isse_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {8E788CEE46SA4B60AE3E1FA31B7036E0}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SowDatePicker: For dates
SorceField: isse_date
Sorce'able: isse
'extAlign: Ceneral
retrn_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {3427SB123F3S4B47B1C3D0B33A7EF2A8}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: S
Reqired: False
SowDatePicker: For dates
SorceField: retrn_date
Sorce'able: isse
'extAlign: Ceneral
retrn Yes/No 1
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Library database management system
113
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 38
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1440
DataUpdatable: 're
DisplayControl: 106
Format: Yes/No
CU!D: {gid {8404863S3EF84SDBA20F230BCB3A1E13}}
OrdinalPosition: 6
Reqired: False
SorceField: retrn
Sorce'able: isse
'extAlign: Ceneral
'able !ndexes
Name Nmber of Fields
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
PrimaryKey 1
Clstered: False
Library database management system
114
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 33
DistinctCont: 1
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
roll_no Ascending
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Library database management system
115
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: member issance istory Page: 40
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
116
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: retrned Page: 41
Properties
DateCreated: 12/14/2010 3:22:23 PN Defaltview: 2
DisplayviewsOnSarePoint 1 DOL: Long binary data
FilterOnLoad: False CU!D: {gid {2F243E6SB2C8
46FD383DD4A4S66S860B}}
HideNewField: False LastUpdated: 12/14/2010 3:24:S0 PN
NaxRecords: 0 NameNap: Long binary data
ODBC'imeot: 60 OrderByOn: False
OrderByOnLoad: 're Orientation: LefttoRigt
RecordLocks: No Locks RecordsAffected: 0
Recordset'ype: Dynaset RetrnsRecords: 're
'otalsRow: False 'ype: 0
Updatable: 're
&$
SELEC' isse.|issance_no], isse.|book_code], isse.|roll_no], isse.|isse_date], isse.|retrn_date],
isse.|retrn]
FRON isse
WHERE (((isse.|retrn])=Yes)),
olumns
Name 'ype Size
issance_no Long !nteger 4
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Ato!ncrement, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: 1
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {EB8CE37F4S0S43ED8S6A33DE43030AF4}}
OrdinalPosition: 0
Reqired: False
SorceField: issance_no
Sorce'able: isse
'extAlign: Ceneral
book_code 'ext S
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
Library database management system
117
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: retrned Page: 42
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {073E1C3423ED41S43B043BF63EF33C70}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 1
Reqired: False
RowSorce: SELEC' |books].|book_code] FRON books,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: book_code
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
roll_no 'ext 3
Aggregate'ype: 1
AllowNltiplevales: False
AllowvaleListEdits: 're
AllowZeroLengt: 're
AppendOnly: False
Attribtes: variable Lengt, Updatable
BondColmn: 1
CollatingOrder: Ceneral
ColmnCont: 1
ColmnHeads: False
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
ColmnWidts: 1440
DataUpdatable: 're
DisplayControl: Combo Box
CU!D: {gid {C640FSC26S634D33B07A34263A3E8ASB}}
!NENode: 0
!NESentenceNode: 3
Limit'oList: False
ListRows: 16
ListWidt: 1440twip
OrdinalPosition: 2
Reqired: False
RowSorce: SELEC' |member].|roll_no] FRON member,
RowSorce'ype: 'able/Qery
SowOnlyRowSorcevale False
SorceField: roll_no
Sorce'able: isse
'extAlign: Ceneral
UnicodeCompression: 're
isse_date Date/'ime 8
Aggregate'ype: 1
Library database management system
118
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: retrned Page: 43
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {8E788CEE46SA4B60AE3E1FA31B7036E0}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 3
Reqired: False
SowDatePicker: For dates
SorceField: isse_date
Sorce'able: isse
'extAlign: Ceneral
retrn_date Date/'ime 8
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: Defalt
DataUpdatable: 're
CU!D: {gid {3427SB123F3S4B47B1C3D0B33A7EF2A8}}
!NENode: 0
!NESentenceNode: 3
OrdinalPosition: 4
Reqired: False
SowDatePicker: For dates
SorceField: retrn_date
Sorce'able: isse
'extAlign: Ceneral
retrn Yes/No 1
Aggregate'ype: 1
AllowZeroLengt: False
AppendOnly: False
Attribtes: Fixed Size, Updatable
CollatingOrder: Ceneral
ColmnHidden: False
ColmnOrder: Defalt
ColmnWidt: 1440
DataUpdatable: 're
DisplayControl: 106
Format: Yes/No
CU!D: {gid {8404863S3EF84SDBA20F230BCB3A1E13}}
OrdinalPosition: S
Reqired: False
SorceField: retrn
Sorce'able: isse
'extAlign: Ceneral
Library database management system
119
D:\Usman A\project\project1a.accdb 'rsday, Febrary 24, 2011
Qery: retrned Page: 44
'able !ndexes
Name Nmber of Fields
booksisse 1
Clstered: False
DistinctCont: 7
Foreign: 're
!gnoreNlls: False
Name: booksisse
Primary: False
Reqired: False
Uniqe: False
Fields:
book_code Ascending
memberisse 1
Clstered: False
DistinctCont: 0
Foreign: 're
!gnoreNlls: False
Name: memberisse
Primary: False
Reqired: False
Uniqe: False
Fields:
roll_no Ascending
PrimaryKey 1
Clstered: False
DistinctCont: 0
Foreign: False
!gnoreNlls: False
Name: PrimaryKey
Primary: 're
Reqired: 're
Uniqe: 're
Fields:
issance_no Ascending
ser Permissions
admin Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
roup Permissions
Admins Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Users Delete, Read Permissions, Set Permissions, Cange Owner, Read Definition,
Write Definition, Read Data, !nsert Data, Update Data, Delete Data
Library database management system
120
System evuIuution
This new computerized system Ior the library has met most oI its objectives. From the views oI
the librarian and my own judgment the system built is quite user Iriendly. The librarian could
easily navigate through the Iorms and decide through the routes where he had to go. The
database has successIully reduced the time consumption. It has been calculated that
computerized method almost takes halI the time oI the manual system and hence this huge
advantage is achieved. The accuracy and integrity oI data has also increased dramatically
although some oI the human errors still prevail. Despite oI that all major errors are pointed out
due to the validation checks. The use oI paperwork has dropped to almost zero.
Working on computer has reduced the workload oI the librarian quite dramatically. It is Ior him
more oI a Iun then a burden to process all the work. The backup oI this system can be easily
made so there is less chance oI the data becoming loss. Addition modiIication and deletion are
very easy to perIorm. Searching Ior Iiles is a very quick job now. Although there could have
been more search criteria Ior the data oI books and members yet all the criteria that are present
still serve the purpose. Duplication oI data has completely been eradicated. The amount oI space
taken by the previous system has been reduced quite according to the plan. The use oI password
has restricted illegal access to student`s Iiles.
The system also has quite a Iew disadvantages. Firstly this system is not Ieasible Ior a long run.
ontinuous maintenance is needed Ior this system. Librarian oIten comes up with problems that
he couldn`t deal with and then I had to solve the problem Ior him. Although the illegal access to
the system has been restricted by the use oI password, someone can still delete the whole
database with just a single command. In such a case the consequences could be havoc. the
librarian is not a skilled person in Iield oI computers so certain viruses or scams can intr5ude into
the system despite the use oI antivirus soItware and cause blunder.
Library database management system
121
System Improvements
#oom Ior improvement is always there in newly designed soItware. Some possible
improvements can be made as Iollows:
O User should not be able to add records on Iorms in Edit Mode.
O Data would be speciIied in a switchboard in a way oI diIIerent section as Entries,
Amendments and #eports. This will give an easier look to the user.
O SoItware should contain a 'Help buttons on each and every part oI database which make
the soItware easier to run Ior a new user.
O SoItware would be able to get out the inIormation about the books remained using the
books and issuing options.
O There should be a search option in the database so that whatever the user searches, iI
anything pertaining to that search is a part oI the database then it should appear.
O Sometimes there are more than one authors Ior a book, option Ior more authors could also
be added.
O There should have been an option to view the issues or the memberships aIter a certain
speciIied date.
O A splash screen or a message should automatically appear whenever the database is run
which would tell about all the deIaulters who have Iailed to return the books.
O There should be an option to change password in the log in page in which the librarian
would have to conIirm the previous password and then the new password.
O The Iields in the Iorm that opens to return the book should not be changeable. Just the
return Iield should be available to click.