DOCSLIB.ORG

Docstar SQL Edition

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 Database to SQL Server Database using UPSIZVB3.EXE 2-39 Chapter 3 Maintenance....................... 3-1 DocSTAR SQL Edition – Technical Documentation 1 -1 Maintenance .....................................................3-2 SQL Server Maintenance ............................ 3-2 Chapter 4 Troubleshooting ................. 4-1 Troubleshooting ..............................................4-2 Error Messages .............................................. 4-2 ODBC & DSN............................................... 4-3 Restoring MASTER Database.................... 4-3 Chapter 5 Utilities............................... 5-1 Utilities...............................................................5-2 Data Manager................................................ 5-2 Concheck........................................................ 5-4 Chapter 6 Glossary ............................. 6-1 Glossary.............................................................6-2 1 -2 DocSTAR SQL Edition – Technical Documentation Chapter 1 Requirements DocSTAR SQL Edition – Technical Documentation 1 -3 Requirements DocSTAR SQL Edition requires: Hardware DocSTAR SQL Server Host Computer DocSTAR Scan Station Network cards, hub, cables, etc. Software Windows NT Server version 4.0 with service pack 4 installed Windows SQL Server 7.0 Standard Edition, with service pack 1 Windows NT client access licenses and SQL Server client access licenses for all users DocSTAR SQL Edition software CD. Contains: DocSTAR SQL Edition Software \DSSQLED, SETUP.EXE DocSTAR ODBC Drivers \DSODBC, SETUP.EXE Microsoft SQL 7 Service Pack 1, \SQL7SP1, SETUP.BAT Microsoft SQL 7 VB3 Fix, \SQL7FIX ASPI Drivers for Windows NT, \ASPINT, INSTASPI.EXE An existing DocSTAR Host can be used as a scan station to a new DocSTAR SQL Server installation. All data in the DocSTAR database can be moved to the new SQL Server Host during installation of the DocSTAR software. You should ensure beforehand that any existing data (document images, etc) recorded on optical media are in a format that will be directly readable under Windows NT. Media formatted with FAT32 may need conversion prior to installation. 1 -4 DocSTAR SQL Edition – Technical Documentation Chapter 2 Setup DocSTAR SQL Edition – Technical Documentation 2 -1 General Setup Guidelines DocSTAR SQL Edition is installed through a very detailed process. The steps needed to install DocSTAR SE on a given machine will vary based on the particular installation and situation. Factors include whether this is a host or remote system, whether this is a new installation, an upgrade from and earlier DocSTAR version using a Jet database, or an update to DocSTAR SE, and whether this installation is happening in the factory or in the field. Below is a table that lists the types of or reasons for installation and the steps appropriate for each situation. The number indicates the order in which the steps should be taken. The sections which follow describe each of the steps. Follow the directions for the steps that are indicated for your situation. Installation Scenarios Host 1. Factory Installation of Host When a new NT DocSTAR SE Server is built at the factory, all the components of DocSTAR must be installed as if this server will be used in a new installation, including a clean, initialized database. This will allow the technicians to thoroughly test the installation. Note: If the new server is installed in a new site, little needs to be done on site. If the server is installed to upgrade an existing installation, additional steps will be taken at that time. 2. Field Configuration of Host – New Site This situation occurs when a new NT DocSTAR SE server is placed at a customer site as a new DocSTAR. This system will not replace any existing systems or be expected to hold the data of another DocSTAR system, even if the customer has other DocSTAR systems in place. Very little has to happen in this situation, beyond physically connecting the server prepared at the factory. 3. Field Conversion of Host – Existing Site When a new NT DocSTAR SE server replaces an existing DocSTAR system additional steps must be taken on-site to move the customer’s data from the existing system to the new server. The process begins with a factory-installed host. The customer’s data is moved to the new host, and then DocSTAR is reinstalled to customize the installation. However, the backbone pieces of NT and SQL Server do not have to be reinstalled. 4. Routine DocSTAR Reinstall on Host – Existing Site Periodically, updates to the DocSTAR SE software will be available. At other times, a technician may choose to reinstall DocSTAR to correct a problem with corrupted files or a similar situation. In this situation, DocSTAR SE can easily be reinstalled, skipping the steps used to build a server from scratch. 5. Field Installation of DocSTAR SE on an existing NT Host– Existing Site There are very few systems in the field that are already use an NT Server. For these situations where a new, factory-built NT Server isn’t needed, steps similar to those used in the factory are needed to install SQL Server and other background software. 6. Field Reinstallation on Bare Host Server– Existing Site 2 -2 DocSTAR SQL Edition – Technical Documentation In the case of an extreme failure, the technician may need to remove all software from a server and rebuild the server, beginning with installing the operating system. This situation will combine steps used in the factory to build a new server with steps used in the field to restore or move data from an existing system to a new one. Remote 1. Initial Installation of DocSTAR SE on Remote station– New or Existing site After the host is installed, the scan, view, and view/file stations can be installed. These are all considered remote stations. All steps for this installation are done on-site. 2. Routine DocSTAR SE reinstall on Remote station – Existing site Similar to a host, updates to the DocSTAR SE software will be available or the technician may choose to reinstall DocSTAR to correct a problem. In this situation, DocSTAR SE can easily be reinstalled, skipping the other steps. Summary of Steps 1. Prepare Existing Host When converting an existing system to DocSTAR SE, some steps are needed to backup current data, etc. to prepare for the move. 2. Install NT Server This involves installing the operating system. It needs only be done when loading a bare machine. 3. Setup SQL Server This involves installing the SQL Server software and setting general configuration options. This is required when building a new system or before installing DocSTAR SE on one of the few NT servers that exist. 4. Copy existing DocSTAR 2.3 data to new NT server This step is necessary when converting a DocSTAR 2.3 system to DocSTAR SE. It is done prior to installing DocSTAR SE so that the original DocSTAR configuration information is used. 5. Configure SQL Database Structures Prior to loading any data, SQL Server requires you to define and configure the databases you will use. This step is required prior to loading any DocSTAR database onto a host. It will be done at the factory, except in cases where SQL Server itself is installed in the field. 6. Install ODBC Drivers These drivers are required on both host and remote stations to communicate with the database. They will be installed on the host at the factory, when possible, and on remote systems on-site. 7. Install DocSTAR SE Similar to other versions, this step will install the DocSTAR-specific family of software on both host or remote systems. This will be the piece used most often. DocSTAR SQL Edition – Technical Documentation 2 -3 8. Database Activity (Initialize, Update, or Upsize) Because the database installation now includes both the database tables and some additional code routines, it needs to be done whenever DocSTAR code is updated on a host. The initialization and update steps are similar to those used in the past. (Previously, one would run INITIALIZE from DocAdmin to initialize or
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • Information Technology Module for Managers Database Design
    Information Technology Module for Managers Database Design Lesson No. 2 In this lesson you will come to know the history of database files and about Relational Database Management System (RDBMS). You will also come to know briefly about Client/Server computing. History of Files: From the inception of computing we know three types of files. They are: Sequential Model Navigational Model Relational Model We are now seeing the emergence of the fourth type: Object Model (along with relational/object hybrids) Along with the above evolution, there has been a shift of responsibility from the application to the database. For example: in sequential model, application was responsible for locating a record and enforcement of business rules. 1.1 Sequential Model Sequential files consist of fixed length records with fixed length fields. The old 80-column cards are example of this. A variation of this came later, when a character was used as a delimiter, instead of depending on the end of a record in fixed location. Visual Basic supports both these forms of sequential files. VB uses Open, Close and other variety of statements. An advantage of this sequential model is its simplicity. On the other hand the disadvantage is that search always begins from the first records and one after the other. Some improvements were introduced later whereby Random search became possible. 1.2 Navigational Model Also called Hierarchical Model. It was a major improvement. The detail of navigation is kept hidden from the developer so that the database did the dirty work of locating a record. Common examples were dBase and Btrieve files.
    [Show full text]
  • Developing a Web Enabled Database System: an Academic Project
    Session 1658 Developing a Web-Enabled Database System: An Academic Project Paul I-Hai Lin - Indiana University-Purdue University Fort Wayne Melissa Lin - University of Florida Aik Mon - GE Industrial Systems ABSTRACT Database and Web integration offers a cost effective way to provide value added access to data stored at multiple locations through a Web browser. This paper discusses two methodologies for implementing a remote database query systems using Web browsers. I. Introduction In May 2000, we developed a Web-enabled alumni database for remote access by our faculty and staff. The alumni database was created from a spread sheet that contains the following fields: Title, Last Name, First Name, Middle Initial, Degree Received, Major, Graduation Date, Address, City, State, Zip code, Email address, Phone, Employer, ID, Last Gift Amount, Last Gift date, and Total Gift Amount. The developed Web-based alumni database has the following capabilities: • View data records for all alumni (20 records per screen) • Find a specific alumnus or group of alumni by their Last Name, First Name, Graduation Date, City, State, or Employer • Update specific fields on alumni data records • Update, delete, and add alumni records to database Although the data warehouse and Web-enabled databases are well known and matured in commercial sector, for us, this is a new challenging and requires additional research. This paper is not intended to provide a comprehensive study report of tools and architectures for building database and Web integration systems. However, the Internet protocols, languages and tools, databases, Web servers, CGI, and server-side scripting are highlighted in various sections to help the selections of programming tools, system platform, Web servers, and databases for this Web- enabled alumni database system.
    [Show full text]
  • Access Upsizing Project, It Is Important to Understand That There Are a Variety of Upsizing Methodologies
    Strategic Initiatives: Evolving Microsoft Access Applications to Microsoft SQL Server Learn When and How to Upsize to SQL Server Prepared by: Dan Haught Executive Vice President FMS Professional Solutions Group www.fmsinc.com/consulting Toll Free (866) 367-7801 Local (703) 356-4700 Strategic IT Initiatives: Evolving Microsoft Access Applications to Microsoft SQL Server Learn When and How to Upsize to SQL Server Dan Haught, Executive Vice President of FMS, is globally recognized as a software development expert and brings extensive experience building database applications using state-of-the-art technology and program management to complex client engagements. Dan has a UNIX/C programming background, and is an expert in Access, VB, SQL, .NET and web development. He is the primary developer of several FMS products, a frequent speaker at industry conferences, and a contributing editor to several monthly magazines including Advisor Access/VB/SQL and ASP.NET PRO. Dan has co-authored several books on software development, including the Microsoft Jet Database Engine Programmer's Guide (Microsoft Press). He is responsible for new product origination, ensures that all FMS products and solutions employ standards-based best practices, and manages the daily operations of the development teams. Dan joined FMS in 1992. Executive Summary This whitepaper explores the issues related to upsizing Microsoft Access applications to take advantage of the performance, security, and reliability of Microsoft SQL Server. Topics discussed include: The Value of Access in Your Organization – a brief discussion of how Access provides power and agility to an organization’s users Making the Decision: When to Upsize – an evaluation of the criteria to decide if an application has outgrown the capabilities of access Microsoft Access Data Architectures – a discussion of the type of data architectures that Access supports Types of Upsizing Projects – There are several approaches to upsizing.
    [Show 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.
    [Show full text]
  • Anlegen Von Datenbanken Im Microsoft SQL Server 2014 Modellbasiertes Forward Engineering Und Migration Von Access-Datenbanken
    Anlegen von Datenbanken im Microsoft SQL Server 2014 Modellbasiertes Forward Engineering und Migration von Access-Datenbanken Manfred Sommer Stand: Februar 2016 Manfred Sommer: Anlegen von Datenbanken im Microsoft SQL Server 2014 1 Inhaltsverzeichnis 1 Einleitung ................................................................................................................... 2 2 Anlegen einer neuen SQL Server Datenbank ......................................................... 2 2.1 Anlegen mit einem Datenmodellierungswerkzeug ...................................................... 3 2.1.1 Logisches und physikalisches ERwin-Modell erzeugen ....................................................... 4 2.1.2 Ziel-Server wählen ................................................................................................................ 5 2.1.3 Ziel-Datenbank mit dem SQL Server Management Studio anlegen ..................................... 6 2.1.4 Mit der SQL Server-Datenbank verbinden ............................................................................ 6 2.1.5 Tabellen mit Forward Engineering anlegen .......................................................................... 8 2.1.6 Synchronisation mit Complete Compare ............................................................................. 10 2.2 Anlegen mit einem SQL-DDL-Skript ........................................................................... 12 2.3 Datenbankdiagramm erzeugen ................................................................................... 15 2.4
    [Show full text]
  • Copyrighted Material
    19_046845 bindex.qxp 3/21/07 9:48 PM Page 527 Index Index Access Projects A based on SQL Server databases, 260, 262–263 ACCDB file format, 2, 29 creating, 259–263 ACCDB files, 253, 278, 281 described, 253 ACCDE file format, 2 displaying new, 278, 284 ACCDE files, 331 as a front end to SQL Server, 253–254 Access 2007 migrating existing Access databases to, 277–284 changes from Access 2003, 2 reusing code across multiple, 308 as a front end to other databases, 132 storage locations for objects seen from, 254 three-tiered applications and, 15 working with SQL Server objects, 264–277 Access 2007 VBA Access runtime, 330 changes from Access 2003, 2–3 Access tables programming concepts, 3–25 checking dates in, 277 uses of, 1 exporting contents to a spreadsheet, 205, 206 Access database files. See ACCDB files ActionSuccess event, 116, 120–121 Access databases Activate event, 247 attaching SharePoint lists to, 231 active plans, retrieving, 472 changes to existing prior to migration, 277 ActiveConnection property, 143, 147, 151, 155 connecting to, 132 ActiveX controls, 305–308 importing a SQL Server database, 203–204 ActiveX Data Objects. See ADO importing data from, 201 Activity Diagrams, 7–8, 9, 10 separating into two database files, 319–322 actor in a Use Case Diagram, 5 upsizing, 277–284 Add Comment button, 337 Access designer, 271 COPYRIGHTEDAdd MATERIAL Current Contact To Project button, 339, 340 Access field data types. See field data types Add method, 112, 113 Access forms, generating prototype screens, add mode, 442–443, 449–450 336–340 Add mode flag, 169, 176 Access macros, VBA instead of or with, 1 Add New navigation button, 137 Access Options, Advanced, 316–317 Add Table dialog box, 275 Access Project file, 278, 281 Add Watch dialog box, 69, 71 19_046845 bindex.qxp 3/21/07 9:48 PM Page 528 AddEmptyProjectRecord procedure AddEmptyProjectRecord procedure, 419, 433 ADP file, opening, 278 Add-in Manager, 313 ADPs.
    [Show full text]
  • Client-Server-Computing.Pdf
    This page intentionally left blank Copyright © 2009, New Age International (P) Ltd., Publishers Published by New Age International (P) Ltd., Publishers All rights reserved. No part of this ebook may be reproduced in any form, by photostat, microfilm, xerography, or any other means, or incorporated into any information retrieval system, electronic or mechanical, without the written permission of the publisher. All inquiries should be emailed to [email protected] ISBN (13) : 978-81-224-2861-2 PUBLISHING FOR ONE WORLD NEW AGE INTERNATIONAL (P) LIMITED, PUBLISHERS 4835/24, Ansari Road, Daryaganj, New Delhi - 110002 Visit us at www.newagepublishers.com Preface In recent years there have been significant advances in the development of high performance personal computer and networks. There is now an identifiable trend in industry toward downsizing that is replacing expensive mainframe computers with more cost-effective networks of personal computer that achieve the same or even better results. This trend has given rise to the architecture of the Client/Server Computing. The term Client/Server was first used in the 1980s in reference to personal computers on a network. The actual Client/Server model started gaining acceptance in the late 1980s. The term Client/Server is used to describe a computing model for the development of computerized systems. This model is based on the distribution of functions between two types of independent and autonomous entities: Server and Client. A Client is any process that request specific services from server processes. A Server is process that provides requested services for Clients. Or in other words, we can say “A client is defined as a requester of services and a server is defined as the provider of services.” A single machine can be both a client and a server depending on the software configuration.
    [Show full text]
  • Recordset for Reporting the Standings
    Structure of Sailors.mdb Introduction and Objective Sailors. mdb supports a hypothetical web site for competitive sailors. The web site includes pages to notify sailors of upcoming regattas, changes in rules, reports on past regattas, and personalized pages based on each sailor's interests. Additional features allow the posting and statistical analysis of regatta results and the ranking of sailors. Vocabulary and Business Rules Sailors, in this database are people who race sailboats. These people have the normal personal information such as names and nationalities, as well as an assigned professional class, which reflects their commitment and accomplishment in the sport of yachting. The most skilled sailors, those of Olympic caliber, are rated Professional Class 1 while those who compete at an amateur level are class 3. Boats are owned by Sailors. A boat has a name and an identifying sail number. Every boat is of a boat class. A Boat Class is a group of boats of the same shape, sail area and hull size, thus ensuring an even competition among the sailors. Sailors generally race in one class only and thus are not interested in information for boats of other classes. Sailors race under the aegis of yacht clubs, the organizations which typically sponsor regattas. Yacht clubs have an identifying flag called a club burgee, may have a web site, and each year a yacht club has a meeting at which time information for the season is disseminated. Larger boats are limited to sailing from clubs with a crane to hoist the boat from its trailer to the water.
    [Show full text]
  • More SOL- Salutions to Common Problems
    APPENDIX A More SOL- Salutions to Common Problems Problem 1: Begin a Label Report at Any Label on the Sheet MosT LABEL RuNs leave unused labels an the last sheet. The following technique will start a label run at a specific label position, so you can use those partially used sheets. The components are a form, a temporary table, and a label report. You'll use the form to identify the position of the first available label. Then, an event procedure will populate the temporary table with blank rows, with one blank row for each missing label. The number of blank rows is determined by the value you enter. Ifyou enter a value of 3 (meaning that the first label is in the third label position), the procedure will add two blank rows. Next, the procedure appends the label data below the blank rows. The report doesn't care that the rows are empty; the positions are still filled in the label report. Each blank row represents a blank label, pushing the actual data down to the first label. This technique doesn't accommodate missing labels between the first and last label. Example: tblOne, frmOne, and rptOne Solution 1: SELECT, DELETE, and INSERT INTO Ta create the temporary table: 1. In the Database window, select the table that contains the data you're printing. 2. Press Ctr1 +C to copy the table to the clipboard. 3. Press Ctrl+V topaste a copy ofthe table. In the Paste Table As dialag box, enter a name for the dummy table. (We'll be working with tblOne.) Select the Structure Only option button in the Paste Options section, and dick onOK.
    [Show full text]