presented by:
Nilesh Joshi

---

[attachment=9214]
SCHOOL MANAGEMENT SYSTEM
B.OBJECTIVE OF THE PROJECT:-
This project has been designed for the School. This simple to use and to manage. All the basic requirements of a School have been fulfilled successfully.
C. LEAST HARDWARE SPECIFICATION:-
System : PIV
Ram : 512 MB
CD Drive : Any One
Key Board : Any (101,104,106)
Monitor : 14’’/15’’ Color Monitor
Operating System : Windows (XP)
D.SOFTWARES USED:-
DEVELOPMENT TOOLS : VISUAL BASIC 6.0
DATABASE : MS-ACCESS
E. ABOUT THE PROJECT :-
This project is maintain the information about School for adding, Deleting and Modify Detail about Student, teacher, Examination, Result, Book department and fees department.
This project provides the facility for book management and fees management. User can store the information about books, students, teachers and fees Submission. It’s also provides the facility for maintain information about students and teacher.
The software uses Ms-Access 8.1.5.0.0 (Enterprise Edition) as the back end and Visual Basic as the front end. The choice of the software was definitely driven by current demand of the software in today’s market.
Visual Basic was instead of Developer 2000 because Visual Basic is not only a front end but also a software development environment or tool So by as front end tool we got a chance to study its various other aspect.
TYPE OF INTRINSIC CONTROL
Static Text
Group Box
Check Box
Scroll Bar
Timer
Folder Hierarchy
Circles abed Stuff
Pictures
Editable Text
Button
Radio Button
Drop Down List
List
Integrated Development Environment Elements :-
The Visual Basic integrated development environment (IDE) consists of the following elements.
Menu Bar
Display the commands you use to work with Visual Basic. Besides the standard File, Edit, View, Windows, and Help menus, menus are provided to access functions specific to programming such as Project, Format, or Debug.
Context Menus
Contain shortcuts to frequently actions. To open a context menu, click the right mouse button on the objects you’re using. The specific list of shortcuts available from context menus depends on the part of the environment where you click the right mouse button. For example, the context menu displayed When you right click on the Toolbox lets you display the components dialog box, hide the Toolbox, dock or undock the Toolbox, or add a custom tab on the Toolbox.
Toolbars
Provide quick access to commonly used commands in the programming environment. You click a button on the Toolbar once to carry out the action represented by that button. By default, the standard Toolbar is displayed when you start Visual Basic. Additional Toolbars for editing, from design, and debugging can be toggled on or off from the Toolbars command on the View menu. Toolbars can be docked beneath the menu bar or “float” if you select the vertical bar on the left edge and drag it away from the menu bar.
Toolbox
Provides a set of tools that you use at design time to place controls on a from. In addition to the default toolbox layout, you can create your own
Custom layouts by selecting add tab from the context menu and adding controls to the resulting tab.
Project Explorer Window
Lists the forms and modules in your current project, a project is the collection of files you to build an application.
Properties Window
Lists the property settings for the selected form or control. A property is a characteristic of an object, such as size, caption, or color.
Form Designer
Serves as a window that you customize to design the interface of your application. You add controls, graphics, and pictures to a form to create the look you want. Each form in your application has its own form designer window.
Object Browser
Lists objects available for use in your project and gives you a quick way to navigate through your code.
Code Editor Window
Server as an editor for entering application code. A separate code editor window is created for each form or code module in your application.
Form Layout Window
The form layout window allows you to position the forms in your application using a small graphical representation of the screen.
Immediate, Locals, and Watch Windows
These additional windows are provided for use in debugging your application. They are only available when you running your application within the IDE.
DATABASE PROGRAMMING IN VISUAL BASIC
DAO :-
Data Access Objects (DAO) can be used either with the Microsoft jet database engine or, using the ODBC direct option, without it. This chapter discusses design and implementation issues that arise when using the Data Access Objects (DAO) to access remote databases. The Microsoft jet database engine is a stand-alone database management system that is capable of both processing queries and routing queries to remote servers as needed. Accessing jet through DAO adds to Microsoft Visual Basic’s ease of development by providing an object-oriented development paradigm and accessibility to data-aware bound controls.
Remote Data Access Using DAO and ODBC Direct
Visual Basic version offers an additional option that can be used with DAO to access remote database engines. ODBC Direct .this DAO option permits your application to choose the database engine and interface used by DAO. Basically, you have to choices:
The Microsoft jet database engine .By default, DAO used jet toper form all data access operations.
ODBC direct. When this option is enabled, DAO loads the Remote Data Object (ROD) 2.0 libraries and delegates all data access operation to the ODBC data source. Basically, ODBC Direct maps each of the data access object to an equivalent remote data object .while not all the RDO functionality is implemented with ODBC direct , this approach permits you to leverage existing DAO-based applications using a familiar object model when accessing remote database system.
Creating Data Sources
A data source is an object that binds other object to data fro man external source. The foundation for a data source object is a data –aware class module, which is essentially a class module that exposes interfaces to an external source of data.
Data –aware classes can also be used as the basis for ActiveX components. One common example of a data aware component is the ADO data control, which provides visual interfaces for binding control to a data through ADO. Although you could create a data aware class that dose same thing as the ADO data control, sharing that class between multiple application and multiple programmers could prove difficult.
A much better approach would be to create an active X component that duplicates or expands on the functionality of the ADO data control .As any Active X component; this could take any one of the several forms: an ActiveX control, an ActiveX DLL, or An active X EXE. In any case, your Active X data source can be easily shared, simplify access to the data regardless of where that data resides: in a local database like Access in a remote database such as SQL, or even in a private OLE DB data store.
The series of step –by-step procedures in the chapter will demonstrative two different approaches to aerating data source components. First we’ll build an ActiveX data.
Source control my data control, which emulates the ADO data control. Next we’ll bind the data control to other control using both simple and complex binding. Finally, we’ll create an ActiveX DLL, My Data that demonstrates binding to a private data store in an OLE DB simple provider.
The procedures for creating the data source components build on each other. The sequence in which you perform the procedures is therefore important.