DOCSLIB.ORG

Software Development with Visual Basic

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Development with Visual Basic B.Com. (C.A.) Third Year Core Paper No. 14 SOFTWARE DEVELOPMENT WITH VISUAL BASIC BHARATHIAR UNIVERSITY SCHOOL OF DISTANCE EDUCATION COIMBATORE – 641 046 1 (Syllabus) B.Com. (Computer Applications) – III Year Core Paper-14 SOFTWARE DEVELOPMENT AND VISUAL BASIC Objectives : To enable the students to develop a front end tool for Customer Interaction in Business. UNIT – I Introduction – Client/Server – Benefits of Client/Server – Downsizing – Upsizing- Right sizing – Client/Server Models – Distributed Presentation – Remote Presentation – Remote Data – Distributed Logic – Distributed Data – Client/Server Architecture – Technical Architecture – Application Architecture – Two Tier Architecture – Three Tier Architecture OLTP & n Tier Architecture. UNIT – II Introduction to Visual Basic – Steps in VB Application – Integrated Development Environment (IDE) – Menu Bar – Tool Bar – Project Explorer Window – Property Window – Toolbox – Properties, Methods and Events – Event Driven Programming – Working with Forms – Variables – Scope of Variables – Constants – Data Types. UNIT – III Functions – Procedures – Control Structure : If – Switch – Select – For – While – Do While – Arrays – User Defined Data Types – Data Type Conversions – Operators – String Functions – Data and Time Functions. UNIT – IV Creating and Using Standard Controls : Form, Label, Text box, Command Button, Check Box, Option Button, List Box, Combo Box, Picture Box, Image Controls, Scroll Bar – Drive List Box – Directory List Box – Time Control, Frame, Shape and Line Controls – Control Arrays – Dialog Boxes – Single Document Interface (SDI) – Multiple Document Interface (MDI) – Menu – Menu Editor – Menu Creation. UNIT – V Data Controls – Data Access Objects (DAO) – Accessing and Manipulating Database – Recordset – Type of Recordset – Creating a Recordset – Modifying, Deleting Records – Finding Records – Data Report – Data Environment – Report – Designer – Connection Object – Command Object – Section of the Data Report Designer – Data Report Controls. 2 CONTENT Lessons PAGE No. UNIT-I 1 Client Server Technology : An Introduction 4 UNIT-II 2 Introduction to Visual Basic 35 3 Integrated Development Environment (IDE) 42 4 Methods and Events 51 UNIT-III 5 Functions 72 6 Define Control Structures 81 7 Arrays 102 8 Operators 110 UNIT-IV 9 Using Standard Controls 122 10 Other Controls 141 11 Timer Controls 152 UNIT-V 12 Using Data Controls 166 13 Record Set 184 14 Data Report 193 3 UNIT - I LESSON-1 CLIENT SERVER TECHNOLOGY : AN INTRODUCTION 1.1 INTRODUCTION The term client/server was first used in the 1980s in reference to personal computers (PCs) on a network. The actual client/server model started gaining acceptance in the late 1980s. The client/server software architecture is a versatile, message-based and modular infrastructure that is intended to improve usability, flexibility, interoperability, and scalability as compared to centralized, mainframe, and time sharing computing . Client/server describes the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfils the request. Although programs within a single computer can use the client/server idea, it is a more important idea in a network. In a network, the client/server model provides a convenient way to interconnect programs that are distributed efficiently across different locations. Computer transactions using the client/server model are very common. For example, to check your bank account from your computer, a client program in your computer forwards your request to a server program at the bank. That program might in turn forward the request to its own client program that sends a request to a database server at another bank computer to retrieve your account balance. The balance is returned back to the bank data client, which in turn serves it back to the client in your personal computer, which displays the information for you. Nearly all the major online information and e-commerce services (sites such as Amazon.com, eBay, Yahoo, MSN, and more) follow the client-server file sharing model. On a smaller scale, most campus services (such as NetFiles, Express Email, Illinois Compass, and Banner) also follow the client-server file sharing model. 4 1.2 DEFINITIONS There are a variety of definitions for the term client/server. The client/server system is defined in terms of individual pieces that work together as a whole and viewed as a system that integrates hardware, software, and networking. This integration of technology is specifically designed to share resources, in support of one or more business functions, in multiple locations simultaneously. As an example is the Internet itself is the world’s largest client/server system. This client/server system is comprised of thousands of clients and servers transferring information and supporting millions of business functions across a network that spans the globe. 1.3 ADVANTAGES OF CLIENT/SERVER ARCHITECTURE The client/server model is particularly recommended for networks requiring a high degree of reliability, the main advantages being: centralised resources: given that the server is the centre of the network, it can manage resources that are common to all users, for example: a central database would be used to avoid problems caused by redundant and inconsistent data improved security: as the number of entry points giving access to data is not so important server level administration: as clients do not play a major role in this model, they require less administration scalable network: thanks to this architecture it is possible to remove or add clients without affecting the operation of the network and without the need for major modification 1.4 DISADVANTAGES OF THE CLIENT/SERVER MODEL Client/Server architecture also has the following drawbacks: increased cost: due to the technical complexity of the server a weak link: the server is the only weak ling in the client/server network, given that the entire network is built around it! Fortunately, the server is highly fault tolerant (primarily thanks to the RAID system) 1.5 CLIENT/SERVER SYSTEM OPERATION A client/server system operates as outlined in the following diagram: 5 The client sends a request to the server using its IP address and the port, which is reserved for a particular service running on the server. The server receives the request and responds using the client IP address and port . Every client/server systems consists of at least one of each of the following: A client that requests information; A server that supplies information; A network that transfer information between the client and the server; The client component of the client/server system can be either hardware or software. In the hardware context, a client is the personal computer functioning as a workstation. This client workstation is capable of stand-alone information processing, which distinguishes it from its mainframe predecessor, the dumb terminal. In the software context, a client is the software that allows to interact with the information residing on the server. Web browsers are examples of software clients, as are email programs (Orifaldi 1996). The server component can also considered both hardware and software. As hardware, the server is typically a personal computer or workstation with enhanced storage capacity. Often, it resides in the same location as the business activity it is required to support. As software, servers have a variety of incarnations, depending on the operational function. For example, windows NT Server acts as a secure server, allowing users to share files and printers over a network. Web servers like Microsoft’s Information Server provides access to and delivery of information over the World Wide Web (Martin 1997). 1.6 MOST CLIENT-SERVER SYSTEMS HAVE THE FOLLOWING DISTINGUISHING CHARACTERISTICS 1. Service: client-server is primarily a relationship between processes running on separate machines. The server process is the provider of services. The client is a consumer of services. In essence, client-server provides a clean separation of function based on the idea of service. 2. Shared resources: a server can service many clients at the same time and regulate their access to shared resources. 6 3. Asymmetrical protocols: there is a one-to-one relationship between clients and servers. Clients always initiate the dialog by requesting a service. Servers are passively waiting on requests from the clients. 4. Transparency of location: the server is a process, which can reside on the same machine as the client or on different machine across the network. Client-server software usually masks the location of the server from the clients by redirecting the service calls when needed. 5. Mix and match: the ideal client-server software is independent of hardware or operating system software platform. One should be able to mix and match client and server platforms. 6. Message-based exchanges: clients and servers are loosely coupled systems which interact through message passing mechanism. The message is the delivery mechanism for the service requests and replies. 7. Encapsulation of services: the server is a specialist. A message tells a server what service is requested and it is up to the server to determine how to get the job done. Servers can be upgraded without affecting the clients as long as the published message interface is not changing. 8. Scalability: client-server systems can be scaled horizontally or vertically. Horizontal scaling
Load more

Recommended publications
  • Visual Basic INTRODUCTION : - Visual Basic Is a Windows Programming Language That Has Developed at Microsoft Corporation
    Visual Basic INTRODUCTION : - Visual Basic is a Windows Programming Language that has developed at Microsoft Corporation. Visual Basic is a powerful programming language to develop sophisticated windows programs very quickly. VB is a one of the RAD (Rapid application development) tools as it enables the programmer to develop application very easily and very quickly. Visual Basic application is very popular as front end to many client/server database systems like SQL/Server, Oracle etc. VISUALBASIC APPLICATION DEVELOPMENT CYCLE:- Decide what you want the computer to do. Decide how you want your program to look on the screen. (The appearance of your program is called the user interface). Draw your user interface by using common component, such as windows, menus and command buttons. (The components of user interface are called objects or controls). Define the name, color, size and appearance of each user interface object. (An object’s characteristics are called properties.) Write instruction in BASIC to make each part of your program do something. (BASIC instructions are called commands). Run your program to see whether it works. Fix any errors (or bugs) in your program. User Interface is what someone sees when program is running. Every program has a user interface in one form or another. A visual Basic user interface consists of forms and objects. A form is nothings more than a window that appears on the screen. Objects are items that appear on a form, such as command button, scroll bar, option button or check box. An object enables the user to give commands to program. Any time a user press a key, moves the mouse, or clicks the mouse button, such an action is called an event.
    [Show full text]
  • Multiview Terminal Emulator User Guide © 2008 by Futuresoft, Inc
    MultiView Terminal Emulator User Guide © 2008 by FutureSoft, Inc. All rights reserved. MultiView User Guide This manual, and the software described in it, is furnished under a license agreement. Information in this document is subject to change without notice and does not represent a commitment on the part of FutureSoft. FutureSoft assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or other wise, without the prior, written per- mission of FutureSoft, Inc. MultiView 2007, MultiView 2000 Server Edition, MultiView 2008 Server Edition, MultiView Catalyst, MultiView License Manager, MultiView DeskTop and Host Support Server are tradenames of FutureSoft, Inc. Edition 1 May 2008 Document #E-MVUG-MV2007-P053108 Last Updated: 102308 FutureSoft, Inc. 12012 Wickchester Lane, Suite 600 Houston, Texas 77079 USA Printed in the USA 1.800.989.8908 [email protected] http://www.futuresoft.com Table of Contents Contents Chapter 1 Introduction Introduction to MultiView 2007 ....................................................................................... 2 Minimum Requirements .................................................................................................. 2 Contacting FutureSoft Support ........................................................................................ 3 Chapter 2 Installation and Configuration Installing MultiView
    [Show full text]
  • Chapter 9 Transact-SQL This Chapter Introduces the Many Options
    Transact-SQL Page 1 of 53 Chapter 9 Transact-SQL This chapter introduces the many options available for working with the SQL query language, along with the extensions and special features of Microsoft SQL Server/MSDE’s SQL dialect. The SQL standard was developed by the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO). Today there are several standards whose names include the year in which they were released: SQL-89, SQL-92, and so on. The different standards vary in language functions and performance. Database vendors have fully or partially implemented the SQL standards in their products. Unfortunately, they have not yet agreed on a unified standard. Almost all have added their own extensions to the SQL implementations, so there are some significant differences among the SQL variations of individual products. Microsoft Access 2000 and Microsoft Access 2002 use Jet Engine 3.6—the database core for Access mdb databases—to support SQL-89 Level 1 with several extensions, as well as SQL-92 (albeit not completely) if you are using Jet Engine 4 with the ADO database interface. SQL Server/MSDE supports SQL-92, which for the most part conforms to the ANSI/ISO standard. The SQL language functions consist of two parts: The Data Definition Language (DDL) and the Data Manipulation Language (DML). With DDL, you can create, edit, and delete table structures and define indexes. The DML is used to query data or to edit and delete data. In Access, you usually only work with the DML, as tables and indexes are created with the tools available in Access.
    [Show full text]
  • Advanced Visual Basic
    Advanced Visual Basic Course Designer and Acquisition Editor Centre for Information Technology and Engineering Manonmaniam Sundaranar University Tirunelveli Client / Server Lecture - 1 Client /Server Objectives In this lecture you will learn the following About Client About Server About Client / Server computing Client / Server Model Centre for Information Technology and Engineering, Manonmaniam Sundaranar University 1 Advanced Visual Basic Lecture Unit - 1 1.1 Snap Shot 1.2 Client 1.3 Server 1.4 Client/ Server Computing 1.5 Client/Server Model 1.6 Short Summary 1.7 Brain Storm Lab unit 1 - ( 2 Real Time Hrs ) 2 Centre for Information Technology and Engineering, Manonmaniam Sundaranar University Client / Server 1.1 Snap Shot Any time two computers are involved in the mutual performance of executing an application, with each performing a different function, you are undoubtedly looking at a client/server application. Many definitions of client/server are used. A definition of client/server application is an application that has a client interface and that accesses data on a remote server. The work is distributed between the client system and the remote server system, based on the capabilities of the client and the system and the remote server system, based on the capabilities of the client and server software applications. Client/server systems usually are efficient because network traffic is minimized and each portion of the application is optimized for a particular function. 1.2 Client A client may be either a device or a user on a network that takes advantages of the services offered by a server. Client is often used in a loose way to refer to a computer on the network.
    [Show full text]
  • The Microsoft Way: COM, OLE/Activex, COM+, and .NET CLR
    8557 Chapter 15 p329-380 8/10/02 12:24 pm Page 329 CHAPTER FIFTEEN The Microsoft way: COM, OLE/ActiveX, COM+, and .NET CLR In a sense, Microsoft is taking the easiest route. Instead of proposing a global standard and hoping to port its own systems to it, it continually re-engineers its existing application and platform base. Component technology is intro- duced gradually, gaining leverage from previous successes, such as the original Visual Basic controls (VBX – non-object-oriented components!), object link- ing and embedding (OLE), OLE database connectivity (ODBC), ActiveX, Microsoft Transaction Server (MTS), or active server pages (ASP). In the standards arena, Microsoft focuses mostly on internet (IETF) and web (W3C) standards. More recently, some of its .NET specifications (CLI and C#) where adopted by ECMA – a European standards body with a fast track to ISO (ECMA, 2001a, 2001b). Microsoft is not trying to align its approaches with OMG or Java standards. While Java figured prominently in Microsoft’s strategy for a while, it has been relegated to a mere continuation of support of its older Visual J++ product – in part as a result of a settlement between Sun and Microsoft. In addition, under the name Visual J# .NET, Microsoft offers a migration tool to .NET, primarily targeting users of Visual J++ 6.0. As part of the .NET initiative, Microsoft is promoting language neutrality as a major tenet of CLR and aims to establish a new language, C#. C# adopts many of the successful traits of Java, while adding several distinctive features of its own (such as value types) and not supporting key Java features (such as inner classes).
    [Show full text]
  • Docstar SQL Edition
    DocSTAR SQL Edition Technical Documentation Chapter 1 Requirements ..................... 1-3 Requirements ...................................................1-4 Hardware ........................................................ 1-4 Software .......................................................... 1-4 Chapter 2 Setup.................................. 2-1 General Setup Guidelines .............................2-2 Installation Scenarios ................................... 2-2 Summary of Steps......................................... 2-3 Installation Steps for Scenarios .................. 2-5 DocSTAR Setup Routine ............................ 2-6 Log files.......................................................... 2-7 Individual Setup Steps ...................................2-9 Prepare Existing DocSTAR Host............... 2-9 Setup NT Server............................................ 2-9 Setup SQL Server ....................................... 2-10 Copy existing DocSTAR 2.3 data to new NT server 2-12 Configure SQL Database Structures........ 2-12 Install ODBC Drivers................................. 2-12 Install DocSTAR SE.................................. 2-13 Database Activity (Initialize, Update, or Upsize) 2-19 Restore DocSTAR SE Data on a Bare NT Server 2-25 Final DocSTAR Steps................................ 2-25 Copy Setup Routines to Host.................... 2-26 Manual Processes......................................... 2-29 Manually Configure SQL Database Structures 2-29 Manually Edit Data Source Names.......... 2-34 Convert Jet
    [Show full text]
  • Experion PKS Dictionary
    Experion PKS Release 516 Dictionary EPDOC-XX29-en-516A August 2020 DISCLAIMER This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright 2020 - Honeywell International Sàrl 2 Contents CONTENTS Contents 3 Chapter 1 - About this Dictionary 49 Chapter 2 - A 51 abnormal states 51 absolute origin block 51 absolute origin 51 access capability 51 access token 51 accumulator point 52 AC 52 ACE 52 ACL 52 acronym 52 action algorithm 53 active connector 53 Active Directory 53 active high 53 active low 54 active memory 54 active parameter 54 active server location 54 ActiveX component 54 ActiveX document 54 activity entity 55 activity 55 3 Contents ADFS 55 administrative privileges 55 advanced alarm management 55 AGA 56 AIC 56 AI 56 AIM 56 alarm/event journal 56 alarm line 56 alarm priority 57 alarm 57 algorithm block 58 algorithm 58 alias table
    [Show full text]
  • Windows Multi-DBMS Programming
    • Windows Multi-DBMS Programming Using C++, Visual Basic®, ODBC, OLE2, and Tools for DBMS Projects Ken North John Wiley & Sons, Inc. New York • Chichester • Brisbane • Toronto • Singapore : . ... • - . Contents Preface XXV Chapter 1 Overview and Introduction 1 The Changing Face of Development 2 Overview 2 Required Hardware and Software 3 Chapter 2 Windows Software Development: Concepts and Issues Terms and Concepts 5 Windows Features and Database Applications 7 Processes, Tasks, and Threads 7 Multitasking 8 Protected Addresses and Safe Multitasking 8 Threads: NetWare and Win32 9 Scheduling 9 Windows Programming 10 Static and Dynamic Linking 11 Dynamic Link Libraries 12 INI Files 12 Resources and Help Files 12 Dialog Boxes 13 Custom Controls 14 Notation 14 Windows Developer's Notebook 15 Baselines 15 Version Control 16 Common Development Steps 16 VH viii Contents Pseudocode 17 Debugging 17 Visual Programming 19 Formal Development Methods 19 Crafting Code for Windows 20 GUI Design Considerations and Database Applications 20 Chapter 3 Database Applications: Concepts and Issues 22 Building Database Applications 22 Database Architectures 23 DBMS Evolution 23 ISAM 24 Network and Hierarchical Databases 24 SQL and Relational Databases 25 Desktop, File Server, and Client-Server 29 Terms and Concepts 30 SQL Concepts 38 Database Design 39 Network Database Design 40 Relational Database Design 40 Query Optimization 45 Issues 48 Sample Database and Applications 49 Info Enterprises 49 Sample Applications 50 Road Map for Database Developers 55 Tools
    [Show full text]
  • Application Techniques
    Application Techniques Appeon PowerBuilder® 2017 R2 FOR WINDOWS DOCUMENT ID: DC37774-01-1700-01 LAST REVISED: January 26, 2018 Copyright © 2018 by Appeon Limited. All rights reserved. This publication pertains to Appeon software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Appeon Limited. Appeon and other Appeon products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Appeon Limited. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP and SAP affiliate company. Java and all Java-based marks are trademarks or registered trademarks of Oracle and/or its affiliates in the U.S. and other countries. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names mentioned may be trademarks of the respective companies with which they are associated. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.
    [Show full text]
  • Developing Multiuser and Enterprise Applications
    26_0672329328_ch22.qxd 5/3/07 3:28 PM Page 909 CHAPTER 22 IN THIS CHAPTER . Why This Chapter Is Important Developing Multiuser . Designing Your Application with Multiuser Issues in Mind and Enterprise . Understanding Access’s Applications Locking Mechanisms . Understanding the Client/Server Model . Deciding Whether to Use the Client/Server Model Why This Chapter Is Important . Understanding the Roles That Many people forge right into the application development Access Plays in the Application process with little worry about the scalability of the appli- Design Model cation. Even a simple application that begins as a single- . Learning the Client/Server user application can develop into a multiuser or Buzzwords enterprise-wide application. Unfortunately, the techniques . Upsizing: What to Worry About you can get away with in the single-user application can wreak havoc in a network or client/server environment. It . Proactively Preparing for is therefore necessary to think about the future when you Upsizing design any application. Although the initial development . Using Transaction Processing process might be more complex, if written properly, the . application will survive any growth that it experiences. Practical Examples: Getting Your Application Ready for an This chapter focuses on writing applications that transition Enterprise Environment easily from the single-user environment through the enter- prise client/server environment. Designing Your Application with Multiuser Issues in Mind When you develop applications that multiple users will access over the network, you must make sure they effec- tively handle sharing data and other application objects. Many options are available for developers when they design multiuser applications, and this chapter covers the pros and cons of these options.
    [Show full text]
  • THE DESAWARE ACTIVEX GALLIMAUFRY Version 2.0 for Visual Basic
    THE DESAWARE ACTIVEX GALLIMAUFRY Version 2.0 for Visual Basic by Desaware, Inc. Rev 2.0.2 (7/01) Page 1 Information in this document is subject to change without notice and does not represent a commitment on the part of Desaware, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only in accordance with the terms of the agreement. It is against the law to copy the software on any medium except as specifically allowed in the license. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Desaware, Inc. Copyright © 1997-2001 by Desaware, Inc. All rightsPage reserved. 2 Printed in the U.S.A. Desaware, Inc. Software License Please read this agreement. If you do not agree to the terms of this license, promptly return the product and all accompanying items to the place from which you obtained them for a full refund. This software is protected by United States copyright laws and international treaty provisions. This program will be licensed to you for your use only. If you, personally, have more than one computer, you may install it on all of your computers as long as there is no possibility of it being used concurrently at more than one location by separate individuals. You may (and should) make archival copies of the software for backup purposes. You may transfer this software and license as long as you include this license, the software and all other materials and retain no copies, and the recipient agrees to the terms of this agreement.
    [Show full text]
  • Windows and Visual Basic1.PDF
    WINDOWS AND VISUAL BASICS CHAPTER ONE 1. Fundamentals of Visual Basic Introduction: A basic is the fastest and easiest way to create applications for Microsoft Windows. Visual Basic provides complete set of tools to simplify rapid application development both for the experienced professional and new window programmers. In the name Visual basic- the “Visual” part refers to the method used to create the graphical user interface (GUI). Unlike many languages which requires numerous lines of coding to describe the appearance and location of interface elements, Visual Basic provides pre-built provides per-built objects that can be used to from the Graphical User interface (GUI). The “Basic” Part refers to the BASIC language as its basic syntax of statements is retained by Visual Basic. But visual basic not contains several hundred statements, functions, and keywords, many of which relate directly to the windows GUI. The Visual Basic programming language is not unique to Visual Basic. The Visual Basic programming system, applications edition included in Microsoft excel. Microsoft access and many other window applications uses the same language. The Visual Basic scripting Edition (VBScript) is a widely used scripting language and a subject of the Visual Basic language. So mastering Visual Basic also helps to master these other areas. New features of Visual Basic 6.0 Whenever a product’s version number increases by one, it means that several enhancements have been made over the previous version. Before looking at the completely new additions to Visual Basic 6.0, this section presents general Visual Basic features briefly. General Features The compiler is Visual Basic gives many different options for optimizing the compiled code, such as Optimization for fat code, optimization for small code and favor of Pentium pro etc.
    [Show full text]