SPECIAL NOTES 1. API PUBLICATIONS NECESSARILY ADDRESS PROBLEMS OF A GENERAL NATURE. WITH RESPECT TO PARTICULAR CIRCUMSTANCES, LOCAL, STATE, AND FEDERAL LAWS AND REGULATIONS SHOULD BE REVIEWED. 2. APIIS NOT UNDERTAKING TO MEET THE DUTIES OF BMPLOYERS, MANU- FACTURERS, OR SUPPLIERS TO WARN AND PROPERLY TRAIN AND EQUIP THEIR EMPLOYEES, AND OTHERS EXPOSED, CONCERNING HEALTH AND SAFETY RISKS AND PRECAUTIONS, NOR UNDERTAKING THEIR OBLIGATIONS UNDER LOCAL, STATE, OR FEDERAL LAWS. 3. INFORMATION CONCERNING SAFETY AND HEALTH RISKS AND PROPER PRECAUTIONS WITH RESPECT TO PARTICULAR MATERIALS AND CONDI- TIONS SHOULD BE OBTAINED FROM THE EMPLOYER, THE MANUFACTURER OR SUPPLIER OF THAT MATERIAL, OR THE MATERIAL SAFETY DATA SHEET. 4. NOTHING CONTAINED IN ANY API PUBLICATION IS TO BE CONSTRUED AS GRANTING ANY RIGHT, BY IMPLICATION OR OTHERWISE, FOR THE MANU- FACTURE, SALE, OR USE OF ANY METHOD, APPARATUS, OR PRODUCT COV- ERED BY LETTERS PATENT. NEITHER SHOULD ANYTHING CONTAINED IN THE PUBLICATION BE CONSTRUED AS INSURING ANYONE AGAINST LIABIL- ITY FOR INFRINGEMENT OF LETTERS PATENT.1.3 Several grades of low alloy steels and ferritic, martensitic, austenitic, and ferritic- austenitic stainless steels are included in this specification. Selection will depend upon design and service requirements. Several of the ferritic/austenitic (duplex) grades are also found in specification A1049/A1049M. 1.4 Supplementary requirements are provided for use when additional testing or inspection is desired. These shall apply only when specified individually by the purchaser in the order. 1.5 This specification is expressed in both inch-pound units and in SI units. However, unless the order specifies the applicable “M” specification designation (SI units), the material shall be furnished to inch-pound units. 1.6 The values stated in either SI units or inch-pound units are to be regarded separately as, the standard. Within the text, the SI units are shown in brackets. The values stated in each system may not be exact equivalents; therefore, each system shall be used independently of the other. Combining values from the two system may result in non- conformance with the standard. 2. Referenced Documents :- 2.1 In addition to the referenced documents listed in specification A961/A961M, the following list of standards apply to this specification. 2.2 ASTM Standard A262 practices for detecting suscepti Steels A275/A275M Practice for magnetic Examination of Steel forgings ‘A336/A336M specification for alloy steel forgings for pressure and high-temperature parts 'y to inter granular attack in Austenitic Stainless3.1 Introduction: The advantage of using tables and relationships ‘common mistake made by inexperienced data- base designers (or those who have more experience with spreadsheets than databases) is to ignore the recommendation to model the domain of interest in terms of entities and relationships and to put all the information they need into a single, large table jure 8.1 shows such a table containing information about courses and sections. + If you have not already done so, open the univ0_vx.mdb database. + Open the Catalog View table. The advantage ofthe single-table approach is that i requires less thought during the initial stages of application development. The disadvantages are too ‘numerous to mention, but some of the most impor- tant ones are listed below: 1 Wasted space — Note that for COMM 290, the ‘same basic course information is repeated for ‘every section. Although the amount of disk space wasted in this case is trivial, this becomes an important issue for very large databases. Difficuity in making changes — What happens if the name of COMM 290 is changed to "Mathe- matical Optimization"? This would require the ‘same change to be made eight times. What ifthe person responsible for making the change for- gets to change all the sections of COMM 290? ‘What then is the “true” name of the course? Deletion problems — What if there is only one ‘section of COMM 290 and itis not offered in a particular year? If section 001 is deleted, then the ‘system no longer contains any information about the course itself, including its name and number of credits.7.1 Introduction: The advantages of forms within forms ‘Accolumnarsingle-column main form with a tabular ‘subform is a natural way of representing information from tables with a one-to-many relationship. For ‘example, the form shown in Figure 7.1 is really two forms: the main form contains information about a ‘specific course; the subform shows all the sections associated with the course. Inthe courses and sect ions example, the foreign key (Deptcode and Crstiur) provides a link between the two forms. This connection allows ‘Access to synchronize the forms, meaning: + when you move to another course record, only the relevant sections are shown in the subform; * when you add a new section, the foreign key in the sections table is automatically filed in (in fact, there is no need to show DeptCode and CrsNvum in the subform). Although you will quickly learn to take a feature such ‘as formisubform synchronization for granted, i is worthwhile to consider what this feature does and ‘what it would take if you had to implement the same, feature using a programming language. 7.2. Learning objectives 17 What is form/subform synchronization? 1 How do | create a form/subform combination? 11 How do inka frm with a subform? 7.3. Tutorial exercises Although there are a number of different ways to ere- ‘ate a subform within a main form, the recommended procedure is the folowing: