The document discusses working in the Forms Developer Environment, identifying the main components like Forms Builder, Forms Compiler, and Forms Services, and how to use Forms Builder to create forms with blocks, items, and canvases, and test forms by running them using Oracle Containers for J2EE. Forms Builder allows building forms with various controls to present and manage data from Oracle databases, and forms can be tested from within Forms Builder by running them using the local OC4J installation and preferences.
Fulcrum is the e-forms engine developed by CDAC Mumbai. The tool can be used to create new forms, modify the existing forms, import forms from any other repository, move forms from one folder to another, copy forms from other folder, etc. It’s a very user friendly tool.
Fulcrum is the e-forms engine developed by CDAC Mumbai. The tool can be used to create new forms, modify the existing forms, import forms from any other repository, move forms from one folder to another, copy forms from other folder, etc. It’s a very user friendly tool.
Open Data Kit, Digital data collection tool, training manual.pptxEbrahimSeid2
The Open Data Kit (ODK), developed by the Department of Computer Science and Engineering at the University of Washington, United Nations of America, is among the commonly used and preferred digital data collection tool by different organizations (especially NGOs). It supports a wide range of questions and answer types, and designed to work well without network connectivity.
Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docxjoyjonna282
Page 1 of 11
A. Lab # : BSBA BIS245A-5B
B. Lab 5B of 7: Completing Forms
C. Lab Overview--Scenario/Summary
TCO(s):
5. Given a physical database containing tables and relationships, create
forms which demonstrate effective user-interface design and allow for
efficient entry and retrieval of data.
Scenario/Summary
The lab begins with creating a form in Access using the Form Wizard. After the
form is created, the user can use Themes to change the appearance of the form.
The second part of the lab uses Form Design to create a form. Finally, the form
will be customized.
Upon completing this lab, you should be able to
• create a form using the Form Tool;
• create a form using Form Design; and
• create a form using the Form Wizard.
D. Deliverables
Submit the MS Access Database file that contains the forms created in this lab.
Step Deliverable Points
1 Form 1 – Form Tool - step-by-step 5
2 Form 2 – Form Design – step-by-step 5
3 Form 3 – Form Wizard—Employee/Customers Multi-Table Form
– step-by-step
5
4 Form 4 – Suppliers and Products Multi-Table Form 10
E. Lab Steps
Preparation
1. Get the Database from Doc Sharing
Page 2 of 11
a. Download the Lab5_Start.accdb Northwind database file from your
course Doc Sharing panel (Labs view), and Save the file to your local
drive.
2. Using Citrix for MS Visio and/or MS Access
a. If you are using the Citrix remote lab, follow the login instructions
located in the iLab tab in Course Home.
b. You will have to upload the Lab5_Start.accdb file to your Citrix folder.
Follow the instructions located on the iLab tab in Course Home.
3. Start MS Access
a. If you are using Citrix, click on Microsoft Office Applications folder.
b. If you are using Visio on a local computer, select Microsoft Office from your
Program Menu.
Lab
Step 1: Using the Form Tool
Select Employees table as in the following figure. You will see the Employees
table highlighted.
Click the Create tab, and then click the Form tool.
Page 3 of 11
After clicking the Form button, a new form is created by Access.
The appearance of the form can be easily modified using the Themes option on
the Design ribbon. As you move your cursor over the various themes, the form
will adjust to preview how the modified form would look. You may select any
theme for your form.
Click the Save button to save the form. Name it Lab5_Form1, and then close the
form.
Step 2: Using the Form Design
Page 4 of 11
Click the Create tab; then, click on Form Design. (Make sure that you do not
have any of the tables selected in the Tables list on the left side of the screen.)
After clicking the Form Design, a new form will be shown as the following
Page 5 of 11
Click the Add Existing Fields
option, and then click Show All
Tables to show all the tables in
the database. Drag and drop
fields from the Custo ...
DeVry University
Student Lab Activity
BIS245 Database Essentials for Business with Lab
A. Student Name:
B. Lab 5A ER Matrix:
Student
Course
Student
none
Enrolls in;
Mandatory
One or more
Course
Is taken by:
Optional
One or more
none
Page 1 of 11
A. Lab # : BSBA BIS245A-5B
B. Lab 5B of 7: Completing Forms
C. Lab Overview--Scenario/Summary
TCO(s):
5. Given a physical database containing tables and relationships, create
forms which demonstrate effective user-interface design and allow for
efficient entry and retrieval of data.
Scenario/Summary
The lab begins with creating a form in Access using the Form Wizard. After the
form is created, the user can use Themes to change the appearance of the form.
The second part of the lab uses Form Design to create a form. Finally, the form
will be customized.
Upon completing this lab, you should be able to
• create a form using the Form Tool;
• create a form using Form Design; and
• create a form using the Form Wizard.
D. Deliverables
Submit the MS Access Database file that contains the forms created in this lab.
Step Deliverable Points
1 Form 1 – Form Tool - step-by-step 5
2 Form 2 – Form Design – step-by-step 5
3 Form 3 – Form Wizard—Employee/Customers Multi-Table Form
– step-by-step
5
4 Form 4 – Suppliers and Products Multi-Table Form 10
E. Lab Steps
Preparation
1. Get the Database from Doc Sharing
Page 2 of 11
a. Download the Lab5_Start.accdb Northwind database file from your
course Doc Sharing panel (Labs view), and Save the file to your local
drive.
2. Using Citrix for MS Visio and/or MS Access
a. If you are using the Citrix remote lab, follow the login instructions
located in the iLab tab in Course Home.
b. You will have to upload the Lab5_Start.accdb file to your Citrix folder.
Follow the instructions located on the iLab tab in Course Home.
3. Start MS Access
a. If you are using Citrix, click on Microsoft Office Applications folder.
b. If you are using Visio on a local computer, select Microsoft Office from your
Program Menu.
Lab
Step 1: Using the Form Tool
Select Employees table as in the following figure. You will see the Employees
table highlighted.
Click the Create tab, and then click the Form tool.
Page 3 of 11
After clicking the Form button, a new form is created by Access.
The appearance of the form can be easily modified using the Themes option on
the Design ribbon. As you move your cursor over the various themes, the form
will adjust to preview how the modified form would look. You may select any
theme for your form.
Click the Save button to save the form. Name it Lab5_Form1, and then close the
form.
Step 2: Using the Form Design
Page 4 of 11
Click the Create tab; then, click on Form Design. (Make sure that you do not
have any of the tables selected in the Tables list on the left side of the screen.).
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
11. Data Blocks A B C A B C Master Data Block D X Y Z Detail Data Block X Y Z Table Table 4 3 6 5 2 1
12.
13. Forms and Data Blocks Block 1 Block 4 Block 1 Block 2 Block 1 Block 1 Single Form Module Multiple Form Modules Form A Form B Open Form Open Form Form C Block 2 Block 3
14.
15. Form Module Hierarchy Module Database Table Column Canvas Window Trigger Program units Trigger Trigger Blocks Frame Item Item Item Window Trigger Program Units
16.
17.
18.
19.
20.
21.
22.
23.
24.
Editor's Notes
Schedule: Timing Topic 25 minutes Lecture 15 minutes Practice 40 minutes Total
Introduction Overview This lesson provides you with an overview of Forms Builder, including a high-level description of its components and object hierarchy. Using this knowledge, you can plan and implement the structure of your form applications.
Forms Builder Key Features Forms Builder is a major component of Oracle Forms Developer. You can use Forms Builder to quickly develop form-based applications for presenting and manipulating data in a variety of ways. Users of Forms Builder applications can: Insert, update, delete, and query data by using a variety of interface items Present data by using text, image, and custom controls, including JavaBeans and Pluggable Java Components Control forms across several windows and database transactions Access comprehensive facilities by using integrated menus Send data directly to Oracle Reports As the designer of Forms Builder applications, you can: Design forms that use a number of data sources, including Oracle databases Build applications quickly and easily by using powerful GUI development tools Design applications for Internet deployment Copy and move objects and their properties easily between applications Use design features such as wizards, the Layout Editor, Object Navigator, and PL/SQL Editor
Forms Builder Executables Forms Builder includes two executables (components) that you can access as the designer of applications. Forms Builder This is the application-building component of Oracle Forms Developer. You can use Forms Builder to design and store the definitions of form, menu, and library documents. While in the Forms Builder, you can invoke the other component, Forms Compiler. You must run the Forms Builder component in a GUI environment in order to use its graphical design facilities. Forms Compiler Once your form is built, use the Forms Compiler. This reads the definition of your module and creates an executable run file. Invoking Forms Builder Executables In a GUI environment, you usually store commands to invoke Forms Builder components in menus and window icons for convenient access. You can also enter these commands on the command line.
Forms Developer Executables (continued) For example: IFBLD90 [my_form] [scott/tiger@my_database] Note: Commands for invoking the product components vary according to platform. Forms Services Because Forms applications are Web based, it is not possible to run them directly from the command line. Instead, they are invoked by typing a URL into a browser or applet viewer command, directed to Forms Services. The files used at run time must already have been compiled by the Forms Compiler component. These files must reside on the middle tier machine in a directory accessible to the Forms Runtime Engine (in FORMS90_PATH ). To test your applications, you also can access Forms Services directly from Forms Builder by setting certain preferences, as described later in this lesson. Instructor Note Explain the components of the product and their relationships .
Forms Developer Module Types A Forms application can consist of many modules—that is, files. A module is a major component of your application and is the basis for storage and ownership. A module owns the rest of the objects in the system. A Forms Developer module can be of the following types: Form: As the main component of an application, the form module presents the objects and data that users can see or interact with. Data items in a form are arranged into records. Menu: A menu module can consist of a hierarchy of menus, each with selectable items. PL/SQL Library: A PL/SQL Library is a collection of PL/SQL program units whose code can be referenced and called from other modules. Object Library: An Object Library is a collection of form objects that you can use in other modules. You can create it to store, maintain, and distribute standard objects that can be reused across the entire development organization.
Forms Builder Module Types (continued) Forms Builder provides the default menu for every form. The default menu includes commands for all basic database operations, such as insert, delete, query, and so on. If your application has specific requirements that are not met by the default menu, you can create a custom menu module. Menu modules are not functional by themselves, but when attached to form modules they can provide a service to the facilities offered by a form, as well as options to invoke facilities elsewhere. PL/SQL Library documents can contain program units that can be used by other form and menu modules. You can build an application from multiple form modules, menu modules, and library documents as needed. Instructor Note Explain the relationship among multiple forms, menus, and libraries.
Forms Builder Components Form modules make up the main “body” of an Oracle Forms Developer application. They can consist of many types of objects, some of which are visible to the user at run time. The three major objects in a form are: Items: These are interface objects that present data values to the user or enable the user to interact with the form, depending upon the item type. There are several different types of items. Items are logically grouped into blocks and visibly arranged on canvases. Blocks: A block is the intermediate building unit for forms. Each form consists of one or more blocks. A block is the logical owner of items, and each item in a form belongs to a block. Items in one block are logically related; for example, they may correspond to columns in the same database table or may need to be part of the same navigation cycle. Blocks therefore provide a mechanism for grouping related items into a functional unit for storing, displaying, and manipulating records.
Forms Builder Components (continued) Canvases: A canvas is a “surface” where visual objects, such as graphics and items, are arranged. A form module can have several canvases (like the pages of a paper form). A canvas can display items from one or more blocks. To see a canvas and its items, you must display the canvas in a window. By default, all canvases in a form appear in the same window (which could mean you see only one canvas at a time), but you can assign separate windows for each canvas so that several canvases can be viewed at once. Note: Items in one block do not need to be physically grouped. They can span many canvases (and windows). Instructor Note A canvas is like a picture portrait, and a window is like a picture frame. Just as you need a picture frame to display a picture portrait, you need a window to display a canvas and its contents.
Navigation in a Form Module When you run a form, you principally navigate by way of items and blocks, not by canvases. Each item has a sequenced position within its block, and each block has a sequenced position in the form. When a user requests to move to the next item in a block, focus will be set on the next item in sequence, wherever that may be. If the next item is on a different canvas, Oracle Forms Developer displays that canvas automatically. Similarly, users can request to move to the next block (or previous block). If the first item in this block resides on another canvas, then that canvas is displayed automatically. Of course, if you can already see the item that you want to move to, then you may click on it directly with the mouse. You can also program mechanisms into the application to enable navigation in other ways.
Types of Blocks In Forms Builder there are two main types of blocks: data blocks and control blocks. Data Blocks When you build database applications with Forms Builder, many of the blocks will be data blocks. A data block is associated with a specific database table (or view), a stored procedure, a FROM clause query, or transactional triggers. If it is based on a table (or view), the data block can be based on only one base table, even though the data block can be programmed to access data from more than one table and data sources. By default, the association between a data block and the database enables the user to automatically access and manipulate data in the database. However, to access data from other tables (nonbase tables), you need to write triggers.
Types of Blocks (continued) Data Blocks (continued) For a base table, Forms Builder can automatically perform the following actions: Creates items in the data block to correspond to columns in the table (These items are data items or base table items.) Produces code in the form to employ the rules of the table’s constraints Generates SQL at run time (implicit SQL) to insert, update, delete, and query rows in the base table, based upon the user’s actions At run time, you can use standard function keys, buttons, menu options, or standard toolbar options to initiate query, insert, update, or delete operations on base tables, and the subsequent commit of the transaction. Control Blocks A control block is not associated with a database, and its items do not relate to any columns within any database table. Its items are called control items. For example, you can create many buttons in your module to initiate certain actions and to logically group these buttons in a control block. Master Versus Detail Blocks To support the relationship between data blocks and their underlying base tables, you can define one data block as the detail (child) of a master (parent) data block. This links primary key and foreign key values across data blocks, and synchronizes the data that these data blocks display. Forms Builder automatically generates the objects and code needed to support master-detail relationships. As the designer, you need only request it. Note: If your application requires it, you can also create independent data blocks in which there is no relationship between the two data blocks. Single-Record Versus Multirecord Blocks You can design a data block to show one record at a time (single-record block) or several records at once (multirecord block). Usually, you create a single-record data block to show master block data and a multirecord data block to show detail block data. In either case, records in a data block that are currently not visible on the screen are stored in a block buffer.
Multi-Block and Multi-Form Applications Typically, a Forms Builder application consists of more than one data block. With more than one data block, you can do the following: Separate the navigation cycle of one group of items from another Map each data block to a different database table (You can have one base table per data block.) Produce a master-detail form, with a master data block and corresponding detail data blocks that are related to the master You can create a large form module with many data blocks. Alternatively, you can create several smaller form modules with fewer data blocks in each. Generally, a modular application with several smaller form modules has the following characteristics: Modules are loaded only when their components are required, thus conserving memory. Maintenance can occur on one module without regenerating or loading the others. Forms can call upon one another, as required.
Many Blocks or Many Forms? (continued) Parallel development can be carried out by different team members on different components. Here are some points to consider when grouping data blocks in the application:
Technical Note A form module is made up of one or more blocks. A data block is based on a database object, such as a table or a view. A data block can contain both data items and control items. A frame can be created to arrange data block items. Each item in a block must appear on a canvas, and each canvas must appear in a window. A form module can have one or more canvases and windows. Using triggers, you can add functionality to your form. Triggers can be written at different levels in a form module. User-named program units enable you to write additional PL/SQL code through procedures, functions, and packages.
The Object Hierarchy You can create many types of objects in a form module. They are discussed in more detail in later lessons. In the following table, note that some objects are associated, even though one might not be “owned” by the other. Instructor Note Point out the above objects to the students, using the Object Navigator.
Starting OC4J Oracle9 i AS Containers for J2EE (OC4J) is Oracle’s Java 2 Enterprise Edition (J2EE) container that executes on any Java Virtual Machine (JVM), the Java interpreter that is provided on each operating system and hardware platform. It is implemented completely in Java, making it lightweight and easy to install. At the same time, it provides complete support for J2EE applications, including servlets, Enterprise JavaBeans, Java Server Pages, and so on. OC4J is ideally suited to run Forms applications. It is included in Oracle9 i Developer Suite to enable you to test your applications, if desired, on the same machine where you are running Forms Builder. In other words, you do not need to install Oracle9 i AS to test your applications. To use OC4J on Windows NT, you start it by executing the batch file provided, called startinst.bat . This file is located in the j2ee\\Oracle9iDS\\ subdirectory of ORACLE_HOME . If you will be testing your applications on your client machine, it is a good idea to set up a shortcut to this batch file, and also to the batch file to stop the OC4J instance, called stopinst.bat .
Starting OC4J (continued) The batch file executes in a separate window; you can minimize this window if desired. Do not close this window, or you will abort the OC4J instance. When you no longer need to run OC4J you can execute the batch file to stop the OC4J instance, called stopinst.bat .
Testing a Form with the Run Form Button The Run Form menu command or button enables you to run a form module in a Web browser from within Forms Builder. This makes it easy to test your application in a three-tier environment, with all components appearing and behaving as they would for a user of the application. You must define some basic information to enable this three-tier testing environment. You set this information in the Preferences dialog that you access from Edit > Preferences. Once the Preferences dialog is open, perform the following steps: Click the Runtime tab. Set the Application Server URL: This must be a URL pointing to the Forms Servlet on the middle tier. Note that it could be on the same machine where you are running Forms Builder, or on a different machine. You can also use the config parameter to specify a named configuration in the Forms Web configuration file (formsweb.cfg by default). Example for the same machine with OC4J running on the default port of 8888: http://127.0.0.1:8888/forms90/f90servlet?config=myapp Set the Web Browser Location (only needed if you want to run in a different browser than the default for your machine).
Summary With Forms Builder, an Oracle Forms Developer component, you can develop form-based applications for presenting and manipulating data in a variety of ways. Forms Builder enables screen-based queries, inserts, updates, and deletes of data. Forms Builder provides powerful GUI and integration features. Applications consist of form modules, menu modules, and library documents. Form modules consist of logical data blocks. A data block is the logical owner of items. Items in one data block do not need to be physically grouped. Items in one data block can span several canvases. You can run a form application from within Forms Builder in order to test it in a browser. You specify the URL to use in the Runtime tab of the Preferences dialog. You can use OC4J on the machine where you are running Forms Builder to test your application, after first starting an OC4J instance.
Practice 3 Overview In this practice session, you set your Forms Builder preferences to use OC4J to test your application on your local machine. You use the Summit application to query the database tables. You also insert, update, and delete data through the application. Note For solutions to this practice, see Practice 2 in Appendix A, “Practice Solutions.” Instructor Note For this and the remainder of the practices, students will run forms from within Forms Builder on their local machines, using OC4J.
Practice 3 1. Start an instance of OC4J. 2. Set the run-time preferences for Forms Builder to use OC4J to test your applications. Set the Application Server URL by pressing Set Default, which will enter the following settings: 3. In Forms Builder, open and run the Customers form located in your local directory. 4. Select Help > Keys from the menu. 5. Click OK to close the Keys window. Execute an unrestricted query and browse through the records that are returned. 6. Execute a restricted query to retrieve information about the customer with the ID of 212. 7. Execute a restricted query to retrieve the customer whose first name is “Meenakshi”. 8. Try each of these restricted queries: Retrieve all cities starting with San. Retrieve all customers based in the USA with a low credit limit. 9. Display the customer details for Harrison Sutherland and click Orders to move to the Orders form module. 10. Click Image Off and notice that the image item is no longer displayed. Click Image On and notice that the image item is displayed. 11. Query only those orders that were submitted online. 12. Move to the fourth record (Product ID 2322) in the Item block of Order 2355 and click Stock. The Inventory block is displayed in a separate window with stock information for that item.
Practice 3 (continued) 13. Close the Stock window. For the customer Harrison Sutherland, insert a new record in the ORDER block, as detailed below. Notice that some items are already populated with default values. Enter the following: 14. Insert a new record in the ITEM block with the following values: 15. Save the new records. 16. Update the order that you have just placed and save the change. 17. Attempt to delete the order that you have just placed. What happens? 18. Delete the line item for your order and save the change. 19. Now attempt to delete your order and save the change. 20. Exit the run-time session and close the browser window.