ONLINE SYSTEM

E- TICKETING

Ex.no:1

Problem Statement

The concept of e-ticketing is rising with the growing technology and fast moving world. Majority of the people today prefer e-tickets because it saves time that earlier people used to waste by standing in long queues and just a print out can be used as a ticket. To book an e-ticket, you need to first register yourself for free with the website . The website is the official site for online booking and checking the status of the running trains as well as availability of the wait listed tickets. For registration choose a user name and password that you can remember. You need to use the same user name and password for future log in. once you log in; you'll see a column, "plan my travel and book my ticket". In that column insert the codes of originating station and the destination. Thereafter choose the journey date, class of accommodation and the type of ticket you want. For e-ticket select the option and click on 'go'. A list of available trains running between the origination station and the destination city is displayed on the website. Select the train you wish to travel in and check the availability status of that particular train. Then click on 'book ticket'. You can also choose the berth you wish to accommodate. Fill in the train number, passenger details and the type of birth you want and then click on 'make payment'. A drop down column will appear for choosing among various means of payment. Click on any one of then and make the payment ensuring the security of your transaction. After successful transaction a confirmation message appears on the screen and then you can take the print out of the ticket.

Ex.no:2

Requirements

(a) FUNCTIONAL REQUIREMENTS: Reservation to get membership to login the system. Checking to check the availability of the flight seats Reservation to book flight seats prior to travels Waiting list to check and confirm whether the ticket is reserved or in waiting list. Passenger details to enter details about passenger. Transaction to pay the ticket fee by means of credit card. Confirmation to get confirmed about the seats reservation. (b) NONFUNCTIONAL REQUIREMENTS: Credit card to pay the tickets The user should have knowledge about browsing. (C). HARDWARE REQUIREMENTS: Processor Hardware RAM DVD RAM Intel Pentium IV-2.0 GHZ. 40 GB (segate) 512mb 1 no.

(D).SOFTWARE REQUIREMENTS: OS Front end Tool Back end Tool windows XP/vista. Rational Rose Enterprise suite, Visual Basic. MS access

Ex. no: 3

Use Cases For Online E- Ticketing System

USE CASE - 1
USECASE: HIGH-LEVEL Scope: the customer requesting flight, choose a preferred flight & seat, Level: user goal Primary actor: customer STACKHOLDER & INTEREST: System & customer: System: 1. System will accept the request from the customer and chosen flight & seats put on hold from the airline database. 1. a it returns confirmation no to the customer. 1 .b displays the UI for the user to the input payment information. Customer: 2 .the customers choose a preferred flight &seat. PRECONDITION: Customer has a list of clause flight the meet there criteria. POSTCONDITION: Customer will have a flight are seating on hold.

MAIN SUCCESS SCENARIO: 1. Customer launches the ETRS application. 2. System will display the user interface for the user to search available flights. 3. Customer selects the origination city, destination city departure date, return date. 4. He also selects one way (or) round0trip flight that be wisher. 5. He also selects a connection flight (or) non-stop flight. 6. Then he submit the criteria to the system 7. System validate the data checks whether all the information are filled and then provide services 8. It shows a list of flights that satisfies the need of the customer. 9. The customer has been presented with option for flights to go to his/her destination 10. The customer chooses a preferred flight & seat. 11. The application put the seat on hold & request payment information from the user. EXTENSION: SYSTEM: 7. System validates the data that is submitted by the customer. 7.1, checks whether the start city & the end city are same or not 7.1.1, if same it displays the error report to the user. Customer response to the system. 7.2, checks whether the data given by the customer are valid

7.2.1, if not valid displays the error report to the system. 7.2.2, customer response to the system. 7.3, check whether all cities and data are filled 7.3.1, if not valid displays the error report to the user. 7.3.2, customer response to the system 10: If the seats are not available. 10.1: system displays the error message seating that the current seat is Unavailable then displays an updated seating chart continuous at basic event2: 10.2: if the flight is not displayed for a long time.. 10.2.1: if the flight is not longer available system displays an error message starting such and displays an updated list of available flight continuous at basic event. SPECIAL REQUIREMENTS: It includes all hardware and software related to this system. SQL HTML VB DATABASE

FREQUENCY OF OCCURANCE: Frequency of occurrence could be nearly continuous. OPEN ISSUES: What are the law variations? Explore the remote service recovery issue.

USE CASE 2
USECASE: request flight information SCOPE: request available flight information LEVEL: User goal PRIMARY ACTOR: customer. STACKHOLDER & INTEREST: 1. CUSTOMER: her request the available flight information to the system 2. SYSTEM: the system inquires the online database about available flight and presents them to the customer. PRECONDITION: Customer must have interest connection and ETRS (E-ticketing reservation system installed) POSTCONDITION: Finally the system presents a list of flight that satisfies the need of the customer. MAIN SUCCESS SCENARIO: 1. Customer launches the ETRS application. 2. System will display the user interface for the user to search available flights. 3. Customer selects the origination city, destination city departure date, return date. 4. He also selects one way (or) round0trip flight that is wisher. 5. He also selects a connection flight (or) non-stop flight. 6. Then he submit the criteria to the system 7. System validate the data checks whether all the information are filled, then provide services 8, it shows a list of flights that satisfies the need of the customer.

EXTENSION: 7. System validates the data that is submitted by the customer. 7.1, checks whether the start city & the end city are same or not 7.1.1, if same it displays the error report to the user. Customer response to the system. 7.2, checks whether the data given by the customer are valid 7.2.1, if not valid displays the error report to the system. 7.2.2, customer response to the system. 7.3, check whether all cities and data are filled 7.3.1, if not valid displays the error report to the user. 7.3.2, customer response to the system SPECIAL REQUIREMENTS: It includes all hardware and software related to this system. SQL HTML VB DATABASE

FREQUENCY OF OCCURANCE: Frequency of occurrence could be nearly continuous. OPEN ISSUES: What are the law variations? Explore the remote service recovery issue...

USECASE -3
USECASE: choose a flight SCOPE: the customer choose a preferred flight & seat LEVEL: user goal Primary actor: customer STACKHOLDER & INTEREST: System & customer: 1. System will accept the request from the customer and chosen flight & seats put on hold from the airline database. 1. a it returns confirmation no to the customer. 1 .b displays the UI for the user to the input payment information. Customer: 2 .the customers choose a preferred flight &seat. PRECONDITION: Customer has a list of clause flight the meet there criteria. POSTCONDITION: Customer will have a flight are seating on hold. MAIN SUCCESS SCENARIO: 1. The customer has been presented with option for flights to go to his/her destination. 2. The customer chooses a preferred flight & seat. 3. The application put the seat on hold & request payment information from the user. EXTENSION: SYSTEM:

1: if the flight is not displayed for a long time 1.1: if the flight is not longer available system displays an error message starting such and displays an updated list of available flight continuous at basic event. 2: If the seats are not available. 2.1: system displays the error message seating that the current seat is unavailable then displays an updated seating chart continuous at basic event2:

SPECIAL REQUIREMENTS: All the hardware and software related to the E-ticketing Internet system, database, etc Technology of occurrence: Frequency of occurrence could be nearly continuous. OPEN ISSUES: What are the law variations? Explore the remote service recovery issue.

USE CASE - 4
USECASE: Book flight Scope Level : Book flight information : user goal

Primary actor: customer Stack holder & Interest: Customer: He confirms flight and inputs preferred payment information Airline Database: He updates the database Credit card authorization: He charge credit card PRECONDITION: Customer has placed flight and seating on hold.

POSTCONDITION: Customer has confirmation number and valid e ticket to travel. Customers credit card will reflect the transaction in the billing statement. MAIN SUCCESS SCENARIO: 1. System is display flight on hold and prompts user for payment information. 2. Customer confirms flight and inputs preferred payment information. 3. System contents the credit card authorization service. 4. System prompts for final verification. 5. Customer confirms transaction. 6. System application sends the request to purchase the ticket(s) 7. System response indicates success with an authorization no signed by the payment authority.

8. System application sends a request in order to find out how to cancel the reservation should a problem occur later in the process. 9. System service provides the customer with a confirmation number and displays the customer ternary and wishes them a good flight. 10. System charge was applied to customers credit card. EXTENSION: 1. Customer is not satisfied with flight arrangement on hold. H e/she will be able to cancel and reschedule continue at use case request flight information. 1.1 System: if the application cannot communicate with the authorization service, the application displays error message informing the customer that communication cannot be made and to try their purchase later continues at basis event. 1.2 System: if the customer payment information cannot be validated the application displays an error message and continues basis even. Invalid data is empty data or incorrect/incomplete credit card information.. SPECIAL REQUIRMENT: It includes all hardwares and softwares related to this system. SQL, HTML, VB TECHNOLOGY USED: Java script HTML SQL XML

FREQUENCY OF OCCURENCE: Frequency of occurrence could be nearly continuous. OPEN ISSUES: What are the law variations?

Explore the remote service recovery issue.

USECASE - 5
USECASE: View history of flight Scope: Level: History of the flight information user goal

Primary actor: customer STACKHOLDER & INTEREST: Customer: He view the detailed information about the flight for selection or to book a flight. PRECONDITION: Customer must have internet connection and ETRS (E-ticketing reservation system) installed POSTCONDITION: Final all the detailed information about the flight will be displayed to satisfy the customer. MAIN SUCCESS SCENARIO: 1. Customer launches the ETRS application. 2. System will display the user interface for the user to search available flights.. 3. All the flight information & seating arrangement &departure time, return time, no of seats cost of the flight, no of the flight etcwill be given detail.. EXTENSION: 2.If the system not displayed the information 2.2, error message will be displayed. 3. Customer not satisfies with the flight arrangement on hold.

3.1, rescheduling is done. 3.2, again he can start it with the use case request flight.

SPECIAL REQUIREMENTS: It includes all hardware and software related to this system. E.g.: VB TECHNOLOGY USED: JAVASCIPT HTML SQL XML

FREQUENCY OF OCCURANCE: Frequency occurrence could be nearly continuous OPEN ISSUES: What are the law variations? Explore the remote service recovery issue

UML USE CASE DIAGRAMS

Use Case diagrams identify the functionality provided by the system (use cases), the users who interact with the system (actors), and the association between the users and the functionality. Use Cases are used in the Analysis phase of software development to articulate the high-level requirements of the system. Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is on what a system does rather than how. The primary goals of Use Case diagrams include:
Providing a high-level view of what the system does Identifying the users ("actors") of the system Determining areas needing human-computer interfaces.

BASIC ELEMENTS
The basic components of Use Case diagrams are the Actor, the Use Case, and the Association.

1. ACTOR
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The role of the user is written beneath the icon. Actors are not limited to humans. If a system communicates with another application, and expects input or delivers output, then that application can also be considered an actor.

2. USE CASE A use case describes a sequence of actions that provide something of measurable value to an actor. A Use Case is functionality provided by the system, typically described as verb + object (e.g. Register Car, Delete User). Use Cases are depicted with an ellipse. The name of the use case is written within the ellipse.

3. ASSOCIATION
Associations are used to link Actors with Use Cases, and indicate that an Actor participates in the Use Case in some form. Associations are depicted by a line connecting the Actor and the Use Case.

EX NO:3 USECASE DIAGRAMS: a)USE CASE DIAGRAMS AT HIGH - LEVEL:

b) USE CASE DIAGRAM TO REQUEST A FLIGHT:

C) USE CASE DIAGRAM TO CHOOSE A FLIGHT:

d) USE CASE DIAGRAM BOOK A FLIGHT :

Ex.no:4

UML Activity Diagram

Activity diagrams are used to document workflows in a system, from the business level down to the operational level. The Activity diagram is a variation of the state diagram where the "states" represent operations, and the transitions represent the activities that happen when the operation is complete. The general purpose of Activity diagrams is to focus on flows driven by internal processing vs. external events.

BASIC ELEMENTS

1. ACTIVITY STATES Activity states mark an action by an object. The notations for these states are rounded rectangles, the same notation as found in State chart diagrams.

2. TRANSITION When an Activity State is completed, processing moves to another Activity State. Transitions are used to mark this movement. Transitions are modeled using arrows.

3. SWIM

LANE

Swim lanes divide activities according to objects by arranging objects in column format and placing activities by that object within that column. Objects are

listed at the top of the column, and vertical bars separate the columns to form the swim lanes.

4. INITIAL STATE The Initial State marks the entry point and the initial Activity State. The notation for the Initial State is the same as in State chart diagrams, a solid circle. There can only be one Initial State on a diagram.

5. FINAL STATE Final States mark the end of the modeled workflow. There can be multiple Final States on a diagram, and these states are modeled using a solid circle surrounded by another circle.

6. SYNCHRONIZATION BAR

Activities often can be done in parallel. To split processing ("fork"), or to resume processing when multiple activities have been completed ("join"), Synchronization Bars are used. These are modeled as solid rectangles, with multiple transitions going in and/or out.

7. Branching A diamond represents a decision with alternate paths. The outgoing alternates should be labeled with a condition or guard expression. You can also label one of the paths "else."

ACTIVITY DIAGRAM 1:

ACTIVITY DIAGRAM 2:

Ex.no:5
UML CLASS DIAGRAMS

UML Class Diagram

A Class diagram in the UML gives an overview of a system by showing its classes and the relationships among them. Class diagrams are static -- they display what interacts but not what happens when they do interact. BASIC ELEMENTS 1. Class A class is a set of objects that share a common structure and common behavior. It is represented by a rectangle divided into three parts: class name, attributes, and operations.. <Class Name> <Attributes> <Operations>

2. Relationships Relationships between classes are the connecting links. Relationships between classes are generally represented in class diagrams by a line or an arrow joining the two classes. UML can represent the following, different types of class relationships
a. Dependency: If A depends on B, then this is shown by a dashed arrow between A and B, with the arrowhead pointing at B:

b. Association: There is an association between two classes if an instance of one class must know about the other in order to perform its work. An association between A and B is shown by a line joining the two classes: A B

c. Aggregation:

Aggregation is an association in which one class belongs to a collection. If B aggregates A, then A is a part of B, but their lifetimes are independent: An aggregation relationship is indicated by placing a white diamond end pointing to the part containing the whole.

A d. Composition:

Composition, on the other hand, is shown by a black diamond on the end of association next to the composite class. If B is composed of A, then B controls the lifetime of A.

e. Generalization:

Generalization is an inheritance link indicating one class is a superclass of the other. A generalization has a triangle pointing to the superclass. An inheritance (generalization/specialization) relationship is indicated in the UML by an arrow with a triangular arrowhead pointing towards the generalized class. If A is a base class, and B and C are classes derived from A, then this would be represented by the following class diagram A

3. Multiplicity The multiplicity of an association end is the number of possible instances of the class associated with a single instance of the other end. Multiplicities are single numbers or ranges of numbers. The multiplicity of a relationship is indicated by a number (or *) placed at the end of an association.

1 A

* B

This table gives the most common multiplicities.

Multiplicit ies 0..1 0..* or * 1 1..*

Meaning zero or one instance. The notation n . . m indicates n to m instances. no limit on the number of instances (including none). exactly one instance at least one instance

4. Navigability A navigability arrow on an association shows which direction the association can be traversed or queried. An OrderDetail can be queried about its Item, but not the other way around. The arrow also lets you know who "owns" the association's implementation; in this case, OrderDetail has an Item. Associations with no navigability arrows are bi-directional.
Every class diagram has classes, associations, and multiplicities. Navigability and roles are optional items placed in a diagram to provide clarity.

5. Naming an Association
To improve the clarity of a class diagram, the association between two objects may be named:

teaches Teacher Lesson

EX NO:6 CLASS DIAGRAM:

The Uml class diagram is to illustrate class interfaces and their actions. They are used for static object modeling, we have already introduced and used their uml diagram while domain modeling. Description of classes: Class: Customer a. Class name: Customer b. Responsibility: To enter the details about reservation. c. Attribute Specification: Login id, password, name, age, date, departure time, arrival time, reservation charges. d. Method Specification: Enter login, enter password, enter details, ticket request, payment details, cancellation. Class: System a. Class Name: System. b. Responsibility: To display details and act as an interface between passenger and database. c. Attribute Specification: System number, rules, seats, and seat no. d. Method specification: Validity check, get Details, show Current Datails.

Class Database: a. Class Name: Database. b. Responsibility: to manage the transaction and reservations.
c. Attribute Specification: Name, gender, age, details, date, place, plane

no, seat no d. Method Specification:

CLASS DIAGRAM

Ex.no:7

UML Interaction Diagrams

Interaction Diagrams describes how group of objects are collaborated with each other.

TWO

TYPES OF

INTERACTION

DIAGRAMS

1. SEQUENCE DIAGRAM 2. COLLABORATION DIAGRAMS

1. SEQUENCE DIAGRAM

Sequence diagrams document the interactions between classes to achieve a result, such as a use case. Because UML is designed for object-oriented programming, these communications between classes are known as messages. The Sequence diagram lists objects horizontally, and time vertically, and models these messages over time.

BASIC ELEMENTS

i) Object
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines indicating the lifetime of the object over time Objects are instances of classes, and are arranged horizontally. The pictorial representation for an Object is a class (a rectangle) with the name prefixed by the object name (optional) and a semi-colon.

ii) Actor

Actors can also communicate with objects, so they too can be listed as a column. An Actor is modeled using the ubiquitous symbol, the stick figure.

iii) Lifeline
The Lifeline identifies the existence of the object over time. The notation for a Lifeline is a vertical dotted line extending from an object.

iv).Activation
Activations, modeled as rectangular boxes on the lifeline, indicate when the object is performing an action.

V)

MESSAGE
Messages, modeled as horizontal arrows between Activations, indicate the

communications between objects.

A) SEQUENCE DIAGRAMS FOR REQUEST A FLIGHT:

B) SEQUENCE DIAGRAMS FORCHOOSE A FLIGHT:

C) SEQUENCE DIAGRAMS FOR BOOK A FLIGHT:

2.COLLOBORATION DIAGRAM
Collaboration diagrams are also interaction diagrams. They convey the same information as sequence diagrams, but they focus on object roles instead of the times that messages are sent

BASIC ELEMENTS

Collaboration diagrams show objects, their links, and their messages. 1. Object An object has state, behavior, and identity. Objects interact through their links to other objects.
The pictorial representation for an Object is a class (a rectangle) with the name prefixed by the object name (optional) and a semi-colon.

2. Link A link is an instance of an association, analogous to an object. Link is represented by a solid line

3. Message A message is the communication carried between two objects that trigger an event.

A) COLLOBORATION DIAGRAMS FOR REQUEST A FLIGHT:

B) COLLOBORATION DIAGRAMS FOR CHOOSE A FLIGHT:

C) COLLOBORATION DIAGRAMS FOR BOOK A FLIGHT:

Ex.no:8

Logical Architecture Diagram

The Logical architecture is large scale organization of software class into packages, subsystem layer. It is called logical architecture because there is no direction about how these elements are display on different operating system.

Ex.no:9

Technical Services Layer

Technical service layer describes the relationship between different actors components of the software process for any admin seek the registration for new visitor. So that the new visitor can login the website and search for book and if need can buy it. ADD A NEW CUSTOMER:
Customer name Divan Nave Cust id age city Tuty Eruvadi Date of reserv 12-4-11 Return date 20-411

VIEW SEAT INFORMATION:

Enrollment in local colleges, 2005 CUST ID DIVYA NAVI TICKET NO 1125 1456 FLIGHT NO 7005 9000 SEAT NO 52 32

Ex.no:10

Domain Objects Layer

After technical services layer, we are going to generate the coding in Rational Rose Enterprise suite. A) AIRPORT : #include "Airport.h" //##ModelId=4D8AE8270242 Airport::flights() { } #ifndef AIRPORT_H_HEADER_INCLUDED_B2753A73 #define AIRPORT_H_HEADER_INCLUDED_B2753A73 //##ModelId=4D8AE7FB036B class Airport { public: //##ModelId=4D8AE8270242 flights(); private: //##ModelId=4D8AE80E032C Name; //##ModelId=4D8AE81A029F Address;

};

B) CUSTOMER: #ifndef CUSTOMER_H_HEADER_INCLUDED_B2751FF0 #define CUSTOMER_H_HEADER_INCLUDED_B2751FF0 #include "Payment.h" //##ModelId=4D8AE5F302DE class Customer : public Payment { public: //##ModelId=4D8AE6410261 search(); //##ModelId=4D8AE649031C submit(); //##ModelId=4D8AE65C02CE book(); //##ModelId=4D8AE662001F cancel(); //##ModelId=4D8AE66B033C pays(); private: //##ModelId=4D8AE62901A5 name; //##ModelId=4D8AE63400EA id;

//##ModelId=4D8AE6390000 address; }; #endif /* CUSTOMER_H_HEADER_INCLUDED_B2751FF0 */ Destination city #ifndef DESTN_CITY_H_HEADER_INCLUDED_B2753ACC #define DESTN_CITY_H_HEADER_INCLUDED_B2753ACC //##ModelId=4D8AE7B8004E class Destn city { public: //##ModelId=4D8AE7E1005D get TIme(); private: //##ModelId=4D8AE7C900FA name; //##ModelId=4D8AE7CD00EA State; //##ModelId=4D8AE7D10399 Country; }; #endif /* DESTN_CITY_H_HEADER_INCLUDED_B2753ACC */ #endif /* AIRPORT_H_HEADER_INCLUDED_B2753A73 */

C) SYSTEM : #ifndef SYSTEM_H_HEADER_INCLUDED_B2752BCF #define SYSTEM_H_HEADER_INCLUDED_B2752BCF //##ModelId=4D8AE83C00AB class System { public: //##ModelId=4D8AE85E0222 validate(); //##ModelId=4D8AE8670109 display(); private: //##ModelId=4D8AE8480148 No; //##ModelId=4D8AE84D02CE OS; //##ModelId=4D8AE8510186 Id; }; #endif /* SYSTEM_H_HEADER_INCLUDED_B2752BCF */

Ex.no:11
i. ADMINISTRATOR:

User Interface Layer

The administrator is used to reserve a ticket for a new visitor for the website. Admin can keep those records update. Admin keep sales record i.e., now much ticket has been sold, and how much transaction has done. ii. CUSTOMER: The customer has to launch the ETRS application in their system.The customer is to authenticate themselves with some specified criteria, that is they has to launch the ETRS Application in their system, then they should submit the criteria about them, if it is valid they administrator will provide the List of Flights available. iii. VISTOR: The visitor can reserve the application form and become a member of the website. The visitor can search for flights and can choose the flights as per their wish.

USER LOGIN:

ADD A NEW CUSTOMER:

ADD A NEW CUSTOMER:

TICKET FORM:

RESERVATION TICKET REPORT:

PARTICULAR CUSTOMER INFORMATION:

VIEW FLIGHT INFORMATION:

AVAILABLE SEATS INFORMATION:

CANCEL TICKET:

VIEW CUSTOMER INFORMATION:

TICKET AMOUNT INFORMATION:

Ex.no:12

UML Component and Deployment Diagram

UML Component Diagram:

Components are slightly fuzzy concept in this uml, because both class and components can be used to model the something. Models the physical components such as source code, executable program, user interface in a design. A graph of the designs components connected by dependency relationships. Components are shown as rectangles with two tabs at the upper left.

UML Deployment Diagram:

Deployment diagram shows the assignment of concrete software artifact to computational nodes. It shows the deployment of software elements to the physical elements. Deployment diagram are useful to communicate or deployment architecture. Two types of nodes 1.Device Node 2. Execution Environment Node

1. Device Node Device nodes are physically computing resources with processing memory and services to execute software,such as typical computer or mobile phones.

2. Execution Environment Node EEN node is software computing resource that runs within an outer node and which itself provides a service to host and execute other executable software elements.

DEPLOYMENT DIAGRAM

Ex.no:13
SOURCE CODE: Login form

Implementation Codings

Private Sub Command1_Click() f Text1.Text = "Admin" And Text2.Text = "Admin" Then Unload Me Load admin admin.Show ElseIf Text1.Text = "Customer" And Text2.Text = "Customer" Then Unload Me Load custmenu custmenu.Show ElseIf Text1.Text = "" And Text2.Text = "" Then Label3.Caption = "UserName / Password are not Entered" ElseIf Text1.Text = "" Or Text2.Text = "" Then Label3.Caption = "Invalid UserName / Password are Entered" End If End Sub Private Sub Command2_Click() End

End Sub View Flight Information Private Sub Combo1_Click() Frame6.Visible = True Frame6.Enabled = False Call main Set rs = New ADODB.Recordset rs.Open "flight", cn, adOpenDynamic, adLockOptimistic c = Combo1.List (Combo1.ListIndex) rs.movefirst While Not rs.EOF If Trim(rs.Fields(0)) = Trim(c) Then txtfname.Text = rs.Fields(1) txtfrom.Text = rs.Fields(2) txtto.Text = rs.Fields(3) txtdep.Text = rs.Fields(4) txtarr.Text = rs.Fields(5) txttrav.Text = rs.Fields(6) End If rs.movenext Wend

End Sub

Private Sub Command1_Click() Unload Me Load admin admin.Show End Sub

Private Sub Form_Load() Frame6.Visible = False Call main Set rs = New ADODB.Recordset rs.Open "flieght", cn, adOpenDynamic, adLockOptimistic rs.movefirst While Not rs.EOF Combo1.AddItem rs.Fields(0) rs.movenext Wend End Sub

View Seat Information Private Sub Command1_Click() If Combo1.Text = "" Then MsgBox "Values are not properly Entered" Else x=0 c = Combo1.List(Combo1.ListIndex) Call main Set rs = New ADODB.Recordset rs.Open "seat", cn, adOpenDynamic, adLockOptimistic rs.movefirst While Not rs.EOF If (Trim(rs.Fields(2)) = Trim(c)) And Trim(rs.Fields(3)) = Trim(dtp1.Value) Then x=x+1 End If rs.movenext Wend Text1.Text = 70 - x End If End Sub

Private Sub Command2_Click() Unload Me Load admin admin.Show End Sub

Private Sub Form_Load() Text1.Enabled = False Call main Set rs = New ADODB.Recordset rs.Open "flieght", cn, adOpenDynamic, adLockOptimistic While Not rs.EOF Combo1.AddItem rs.Fields(0) rs.movenext Wend End Sub

Conclusion:
Thus the project for ONLINE E- TICKETING SYSTEM has been successfully executed and codes are generated.