Nishant Project (int Visual Basic)

DECLARATION

I hereby declare that the minor project work entitled “FACULTY MANAGEMENT

SYSTEM” submitted for the BCA (5th semester) is my original work carried out by me

under the guidance of Mr. Hari Mohan Jain Sir for the partial fulfilment of the award of

the degree of the Bachelor of Computer Applications. The matter embodied in this report

has not submitted anywhere else for the award of any other degree/diploma and is

original in all respects.

Place: TRINITY INSTITUTE OF PROFESSIONAL STUDIES

Date: November 18, 2009

Nishant Kumaria

(0412062007, B.C.A-5th Semester)

N ishant K umaria’s “ F aculty M anagement S ystem”

Acknowledgement

I would like to thank my parents for there extreme support in formatting the file &

making the task triumph. I will also extend my gratitude to the almighty without which

the project may have not completed. And finally thanks to Mr. Hari Mohan Jain, my

professor for his support in accomplishing the project nicely he has always helped me

whenever I’ve been into petite nuisance.

Thanks…

[Nishant Kumaria]


Abstract

Faculty Management could not have started this journey into the veins of administrative tasks

of an academic institution without the inclusion of the under-listed vital features in my software.

This system is called as Faculty Management System. Faculty Management System

manages the faculty information by accepting adding, modifying or removing (i.e. processing)

information and generating reports.

Add, Edit or Delete Faculty forms.

Generating I-Cards of the faculty.

Faculty Management System captures the faculty personal information such as, Name, Faculty

I’d, Gender, Date of Birth, Faculty Photo, and faculty post. It is integrated so that administration

can share this vital information of Faculties. Access to real-time information is vital for making

informed, data driven decision, both by the Faculties & school administrators and the parents

to have knowledge of the Faculty & other staff in the institution.

The project has been erected using Visual Basic 6.0 as front

end, and Ms Access as back end. The designing of the project has entirely been done by using

the intrinsic & extrinsic tools. And the connectivity is done using “Adodc”.


Index

Chapter number Contents

1. Introduction to “Visual Basic 6.0”,

1.1 Summary of Visual Basic 6.0.

1.2 Language Features.

1.3 Characteristics.

2. Accessing Database Ms Access,

2.1 Setting up an ODBC Data Source.

2.2 Using the ADO Data Control (ADODC).

2.3 Using ADO Code.

3. dfd of the Faculty Management System.

4. Output of the Software.

5. Tables used in the software.

6. Limitation of the Software.

7. Bibliography.


1. Introduction to Visual Basic 6.0

1.1 Summery of Visual Basic 6.0

Visual Basic (VB) is the third-generation event-driven programming language and integrated

development environment (IDE) from Microsoft for its COM programming model. VB is also

considered a relatively easy to learn and use programming language, because of its graphical

development features and BASIC heritage.

Visual Basic was derived from BASIC and enables the rapid application development (RAD) of

graphical user interface (GUI) applications, access to databases using Data Access Objects, Remote

Data Objects, or ActiveX Data Objects, and creation of ActiveX controls and objects. Scripting

languages such as VBA and VBScript are syntactically similar to Visual Basic, but perform differently.

A programmer can put together an application using the components provided with Visual Basic itself.

Programs written in Visual Basic can also use the Windows API, but doing so requires external function

declarations.

The final release was version 6 in 1998. Microsoft's extended support ended in March 2008 and the

designated successor was Visual Basic .NET (now known simply as Visual Basic).

1.2 Language Features.

Like the BASIC programming language, Visual Basic was designed to be easily learned and used by

beginner programmers. The language not only allows programmers to create simple GUI applications,

but can also develop complex applications. Programming in VB is a combination of visually arranging

components or controls on a form, specifying attributes and actions of those components, and writing

additional lines of code for more functionality. Since default attributes and actions are defined for the

components, a simple program can be created without the programmer having to write many lines of

code. Performance problems were experienced by earlier versions, but with faster computers and native

code compilation this has become less of an issue.


Although programs can be compiled into native code executables from version 5 onwards, they still

require the presence of runtime libraries of approximately 1 MB in size. This runtime is included by

default in Windows 2000 and later, but for earlier versions of Windows like 95/98/NT it must be

distributed together with the executable.

Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text boxes,

buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them.

Default values are provided when the control is created, but may be changed by the programmer. Many

attribute values can be modified during run time based on user actions or changes in the environment,

providing a dynamic application. For example, code can be inserted into the form resize event handler to

reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting

code into the event handler for a key press in a text box, the program can automatically translate the case

of the text being entered, or even prevent certain characters from being inserted.

Visual Basic can create executables (EXE files), ActiveX controls, or DLL files, but is primarily used to

develop Windows applications and to interface database systems. Dialog boxes with less functionality

can be used to provide pop-up capabilities. Controls provide the basic functionality of the application,

while programmers can insert additional logic within the appropriate event handlers. For example, a

drop-down combination box will automatically display its list and allow the user to select any element.

An event handler is called when an item is selected, which can then execute additional code created by

the programmer to perform some action based on which element was selected, such as populating a

related list.

Alternatively, a Visual Basic component can have no user interface, and instead provide ActiveX objects

to other programs via Component Object Model (COM). This allows for server-side processing or an

add-in module.

The language is garbage collected using reference counting, has a large library of utility objects, and has

basic object oriented support. Since the more common components are included in the default project

template, the programmer seldom needs to specify additional libraries. Unlike many other programming

languages, Visual Basic is generally not case sensitive, although it will transform keywords into a

standard case configuration and force the case of variable names to conform to the case of the entry

within the symbol table. String comparisons are case sensitive by default, but can be made case

insensitive if so desired.


The Visual Basic compiler is shared with other Visual Studio languages (C, C++), but restrictions in the

IDE do not allow the creation of some targets (Windows model DLLs) and threading models.

1.3 Characteristics.

Visual Basic has the following traits which differ from C-derived languages:

Multiple assignment available in C language is not possible. A = B = C does not imply that the

values of A, B and C are equalled. The boolean result of "Is B = C?" is stored in A. The result

stored in A could therefore be false(0) or true(-1)

Boolean constant True has numeric value −1. This is because the Boolean data type is stored as a

16-bit signed integer. In this construct −1 evaluates to 16 binary 1s (the Boolean value True), and

0 as 16 0s (the Boolean value False). This is apparent when performing a Not operation on a 16

bit signed integer value 0 which will return the integer value −1, in other words True = Not

False. This inherent functionality becomes especially useful when performing logical operations

on the individual bits of an integer such as And, Or, Xor and Not. This definition of True is also

consistent with BASIC since the early 1970s Microsoft BASIC implementation and is also

related to the characteristics of CPU instructions at the time.

Logical and bitwise operators are unified. This is unlike some C-derived languages (such as

Perl), which have separate logical and bitwise operators. This again is a traditional feature of

BASIC.

Variable array base. Arrays are declared by specifying the upper and lower bounds in a way

similar to Pascal and FORTRAN. It is also possible to use the Option Base statement to set the

default lower bound. Use of the Option Base statement can lead to confusion when reading

Visual Basic code and is best avoided by always explicitly specifying the lower bound of the

array. This lower bound is not limited to 0 or 1, because it can also be set by declaration. In this

way, both the lower and upper bounds are programmable. In more subscript-limited languages,

the lower bound of the array is not variable. This uncommon trait does exist in Visual

Basic .NET but not in VBScript.


OPTION BASE was introduced by ANSI, with the standard for ANSI Minimal BASIC in the

late 1970s.

Relatively strong integration with the Windows operating system and the Component Object

Model.

Banker's rounding as the default behavior when converting real numbers to integers with the

Round function.

Integers are automatically promoted to reals in expressions involving the normal division

operator (/) so that division of an odd integer by an even integer produces the intuitively correct

result. There is a specific integer divide operator (\) which does truncate.

By default, if a variable has not been declared or if no type declaration character is specified, the

variable is of type Variant. However this can be changed with Deftype statements such as DefInt,

DefBool, DefVar, DefObj, DefStr. There are 12 Deftype statements in total offered by Visual

Basic 6.0. The default type may be overridden for a specific declaration by using a special suffix

character on the variable name (# for Double, ! for Single, & for Long, % for Integer, $ for

String, and @ for Currency) or using the key phrase As (type). VB can also be set in a mode that

only explicitly declared variables can be used with the command Option Explicit.


2. Accessing Database through ADO

Now days, almost any time you write full fledged database application you will want to use ADO.

Along with this, as your applications become more and more complex you will probably not want to rely

on Visual Basic's data controls, but instead use the ADO objects directly. Read on to find out exactly

how this can be done.

Prior to VB6 and the introduction of ADO (ActiveX Data Objects), VB programmers would generally

use DAO (Data Access Objects) to interact with local databases such as MS Access and use RDO

(Remote Data Objects) to interact with client/server databases such as Oracle and SQL Server. The

concept behind Visual Basic ADO was Universal Data Access (UDA), where one database access

method could be used for any data source; it was designed to replace both DAO and RDO. DAO

remains a viable technology for interacting with MS Access databases as it is faster than ADO for that

purpose; however, ADO is more flexible – using ADO, one could develop a prototype database

application using MS Access in the back-end, and with a "flick of the wrist" (i.e., with very little coding

changes) "upsize" that same application to use Oracle or SQL Server. As far as RDO is concerned, no

new versions of it have been developed beyond the version that shipped with Visual Basic, and there are

no future plans for it.

In the VB4 and VB5 worlds, RDO was the main method used to interact with client/server databases.

RDO works perfectly fine with VB6, so when folks migrated their VB5 applications over to VB6, little

or no coding changes were required. However, ADO is the preferred method of database access for new

VB6 applications.

The first sample application introduces the ADO Data Control (ADODC) which demonstrates a "quick

and dirty" way to connect to a remote database. The second and third applications use ADO code: the

second allows navigation and searching of a database table; the third allows navigation and updating on

a database table. All three connect to an ODBC Data Source, which must be set up through the Windows

Control Panel. How to do this is described below.


Note: If you have previously set up a DSN for the Biblio database as described in the previous topic on

RDO, you can skip the section on setting up an ODBC data source.

2.1 Setting Up an ODBC Data Source

Follow the steps below to set up an ODBC Data Source (this process is also called "setting up a DSN",

where "DSN" stands for "Data Source Name"). These steps assume Windows 2000 for the operating

system. On other versions of Windows, some steps may vary slightly.

Via Windows Control Panel, double-click on Administrative Tools, then Data Sources

(ODBC). The ODBC Data Source Administrator screen is displayed, as shown below. Click on the

System DSN tab.

Click the Add button. The Create New Data Source dialog box will appear. Select Microsoft

Access Driver (*.mdb) from the list and click the Finish button.


The ODBC Microsoft Access Setup dialog box will appear. For Data Source Name, type

Biblio. If desired, you can type an entry for Description, but this is not required.


Click the Select button. The Select Database dialog box appears. On a default installation of

VB6 or Visual Studio 6, the BIBLIO.MDB sample database should reside in the folder C:\Program

Files\Microsoft Visual Studio\VB98. Navigate to that folder, select BIBLIO.MDB from the file list,

and click OK.

Note: If VB was installed in a different location on your system, navigate to the appropriate folder. If

you do not have the BIBLIO.MDB sample database file on your system at all, you can download

it here. In that case, copy the file to the folder of your choice, and navigate to that folder to select

the database for this step.

When you are returned to the ODBC Microsoft Access Setup screen, the database you selected

should be reflected as shown below. Click OK to dismiss this screen.


http://www.vb6.us/files/VBPrograms/BIBLIO.zip

When you are returned to the ODBC Data Source Administrator screen, the new DSN should

appear as shown below. Click OK to dismiss this screen.


At this point, the Biblio database is ready to be used with RDO in the sample application.

2.2 Using the ADO Data Control (ADODC)

To build the first sample application, follow the steps below.

Start a new VB project, and from the Components dialog box (invoked from the Project ->

Components menu), select Microsoft ADO Data Control 6.0 (SPx) as shown below and click OK.

The ADO Data Control should appear in your toolbox as shown below:


Put an ADO Data Control on your form, and set the properties as follows:

Property Value

Name adoBiblio

DataSourceName Biblio

SQL select * from Faculty

Now put three text boxes on the form, and set their Name, DataSource, and DataField properties

as follows:

Name DataSource DataField


txtName adoBiblio Name

txtid adoBiblio ID

txtDob adoBiblio Date of Birth

Save and run the program. Notice how it works just like the other data control.

Now change the SQL property of the data control to select * from Faculty order by Name and

run the program again. Notice the difference.

Change the SQL property back to what it was and add three command buttons to the form, and

set their Name and Caption properties as follows:

Name Caption

cmdNameOrder Order by Name

cmdYearOrder Order by Date of Birth

cmdIDOrder Order by ID

Put the following code in the cmdNameOrder_Click event:

adoBiblio.SQL = "select * from Faculty order by Name"

adoBiblio.Refresh


Put the following code in the cmdYearOrder_Click event:

adoBiblio.SQL = "select * from Faculty order by [year born]"

adoBiblio.Refresh

Put the following code in the cmdIDOrder_Click event:

adoBiblio.SQL = "select * from Faculty order by Date_of_birth"

adoBiblio.Refresh

Save and run the program and see what happens when you click the buttons.

A screen-shot of the sample app at run-time is shown below:


2.3 Using ADO Code

The Property database contains just one table called "Faculty". The columns of this table are defined as

follows:

Column Name Data Type Notes

FirstName Text(200) Name of the Faculty

Fid Number (Long Integer) A number that uniquely identifies the

Faculty. It is a primary factor, and the serves

as the major backbone of the software.

Gender Text (2) Gender of the Faculty, (Male, or Female)

Grade Text (2) It stores the grade of the faculty which

indicates how authorised the faculty is, e.g.

Head of Department, Director,

Administrator Officer, or Chairmen.

DateOfBirth Date & Time Stores the Date of Birth of the Faculty.

PictureFile Text (15) The descriptive location of the Faculty.

(1) On the ODBC Microsoft Access Setup dialog box, type PropDB for the Data Source Name.

(2) In the Select Database dialog box, navigate to the location where you have placed the Faculty.MDB

file.

From the Project -> References menu, check Microsoft ActiveX Data Objects 2.x (where x is

the highest version that you have on your system) and click OK.


This project uses the StatusBar control, so include the Microsoft Windows Common Controls

6.0 (SP6) from the Components dialog box, accessed from the Project -> Components menu.


Create the form shown below. The names of the text boxes in the top frame are shown in the

form. Set the Enabled property of the frame to False, which will automatically disable all of the

textboxes within it, which is desired because this application does not allow updating of the data.

The settings for the other controls are given below.


4. dfd of the Faculty Management System

0-level dfd, Faculty Management System.

A data flow diagram (DFD) is a design tool to represent the flow of data through an information

system.

A "context level" DFD can be used to show the interaction between a system and outside entities; it can

also show the internal data flows within a system. This version is also called a context diagram. It often

shows the information system as a single circular shape with no details of its inner workings: what it

shows is its relationships with the external entities.

With a dataflow diagram, developers can map how a system will operate, what the system will

accomplish and how the system will be implemented. It's important to have a clear idea of where and

how data is processed in a system to avoid double-handling and bottlenecks. A DFD also helps

management organise and prioritise data handling procedures and staffing requirements.

A DFD lets a system analyst study how existing systems work, locate possible areas prone to failure,

track faulty procedures and reorganise components to achieve better efficiency or effectiveness.


Components

A data flow diagram graphically represents:

processes - jobs that are done with the data. A process transforms incoming data flow into

outgoing data flow.

data stores - files, databases, archives. They can be manual, digital or temporary.

external entities/terminators in a business or other system - other systems or people beyond the

control of the current system. These are the places which provide the organisation with data, or

have data sent to them by the organisation (e.g. customers, partners, government bodies).

External entities are sources and destinations of the system's inputs and outputs.

connecting data flows - arrows show how data flows from one place to another. Flows that

cross the system boundary are known as Input Output Descriptions. Label the arrows with the

name of the data that moves through it.

(DFDs can also show resource flows, but it's better to avoid them in VCE IT - they can easily get

confused with data flows.)


4. Output of the Software

The Splash Form, which is indicated at the beginning.


This is the main view of the software and the indicated features are its scope.


This is the view of the software when we click on the edit command.


The software generates the I-d card of the Faculty which holds the indicated features.


Now, that one can also create the faculty and also edit the details then click save.


One, can also delete the faculty by just clicking the delete option.


5. Table used in the Software

The Property database contains just one table called "Faculty". The columns of this table are defined as

follows:

Column Name Data Type Notes

FirstName Text(200) Name of the Faculty

Fid Number (Long Integer) A number that uniquely identifies the

Faculty. It is a primary factor, and the serves

as the major backbone of the software.

Gender Text (2) Gender of the Faculty, (Male, or Female)

Grade Text (2) It stores the grade of the faculty which

indicates how authorised the faculty is, e.g.

Head of Department, Director,

Administrator Officer, or Chairmen.

DateOfBirth Date & Time Stores the Date of Birth of the Faculty.

PictureFile Text (15) The descriptive location of the Faculty.


6. Limitation of the Software

1. Modem and Telephony Card Issues.Many voice modems have poor audio playback quality. The problem: Audio quality is important for creating clear, understandable content for the telephone. Unfortunately, most voice modems have poor audio quality and no volume adjustments. To make matters worse, regular telephone lines are restricted to low audio sampling rates which degrade audio even further.

2. Speech Recognition IssuesSpeech Recognition technology is not supported by the software.

3. Software Development IssuesComponent-based development leaves some factors out of our control.


7. Bibliography1. An Introduction to vb6 Programming, by Bjorn Fahller.

2. An overview of the vb6 Programming Language, by Bjarne Stroustrup.

3. How to think like a computer scientist with vb, by Allen B. Downey.

4. Introduction to O based using vb, by Peter Miller.

5. A beginner’s vb6, by Neil Gray.

6. Programming in vb6 - Rules & Recommendations, by FN/Mats Henricson and Erik.

7. Thinking in vb6 Volume 1- Introduction to standard vb, by Bruce Eckel.


Documents

Nishant Project (int Visual Basic)