If you are storing data in an RDBMS (Oracle, SQL Server, etc), check this page for some tips on optimizing performance.
Release 5.3 added the 0DX application, a tool for importing XML formatted files.
Release 5.2 added some significant new capabilities to the user interface, including Tables
, Drag & Drop Support
, new GUI Events
and the ability to create a subroutine
Release 5.1 added an API to interface with the Chart Director
Release 5.1 added a library of API's to handle common programming tasks. These replace the older ',RT' calls and should be used instead. This link shows the current list of all available API's
, not just the ones released in 5.1.
This page discusses how APPX handles character encoding
How to use custom fonts (such as bar codes) in PDF Outputs.
Widget macros allow you to access some advanced GUI features such as controlling layering, drop shadows, moveable buttons, and more.
This page has some sample VB code showing how to access APPX/IO data via ODBC
The APPX runtime environment includes many standard screens, Scan screens, Disposition screens, etc. This page
shows how you can customize these to more closely resemble your applications.
This page discusses how APPX handles background processing and how you can customize it.
This page discusses a technique for uploading data from a spreadsheet into APPX.
An explanation of how APPX handles GOSUB statements that call SUBRoutine processes.
A discussion of the advantages of using OUTPUT processes instead of UPDATEs for posts and similar activities.
A method for converting an Array (multi-occurence data) to Scalar (single-occurence data)
A collection of instructions and hints for the execution of Windows functions from within APPX.
Instructions on how to display User/Date Stamps in your applications
Instructions on how to tie an existing Inquiry process to a Scrolling Input as an Automatic (or Optional) Child
A variety of methods for importing data from external consecutive files into APPX.
The list of current processes that have called each other is called a "Process Stack". This document describes the Process Stack, how to view it, and what it means.
A discussion on the use of the Pre-Display/Verify Event Point, and how it compares and contrasts with the individual Pre-Display Event Point and the Verify Event Point.
Instructions on copying all (or some) records from a file in one database into the same file in another database.
Describes in detail the use of PASS and CALL statements to access O/S API functions from APPX subroutines.
APPX 4.1 introduced the ability to create and access a cached instance of a file in memory. This document describes how to take advantage of this feature, and the statements required to do so.
The Query specifications used to produce a report are stored in three memory files. This document describes their structure and how to modify and use their values.
APPX 3.x provides the ability to record (and playback) Keystroke and Process logs. You can set up an environmental variable to record Keystrokes and Processes.
An overview of APPX 3.4's approach to calling External Functions, Dynamic Linking, and related topics.
APPX Query is an enduser oriented Report Generator, included with APPX. It allows endusers to define their own reports, without programmer assistance. This document steps you through the process of configuring the APPX Query environment.
There are three levels of Scoping: SUBPROCESS, RELATED, and DETACHED. 'Scoping' refers to what workfields and temporary files (both disk and memory) are available to a given process.
These are UNSUPPORTED
features used to call operating system functions, and they may be changed or removed at any time. Although these may give you information useful towards fulfilling your needs, APPX Software is not responsible for the maintenance or support of these functions.
With the advent of the APPX Desktop Client, a broad range of features were introduced that opened up integration between APPX and the desktop. One of the most useful features is client-side printing. In this issue’s Tech Tip we will explore some of the options and the workings of using client side printing.
There have been a lot of inquiries on how to create a form overlay in APPX.
A PDF form overlay is a predefined image, or electronic form, that is printed underneath the data associated with the process. The use of form overlays eliminates the need for preprinted forms or creating the forms from scratch in Application Design. This article explains the basic concepts of creating an output process using a form overlay.
How many times have you gotten this call: “I need APPX to print me a list . . .”. You throw together an output and route it to the user’s printer, and . . . Argg, the report didn’t print! In this issue, we will talk about where to start troubleshooting a printing problem. We will cover printing text outputs only. We will cover PDF printing at a later time.
This issue we will talk about how to take advantage of that extra room by designing scrolling inputs that adjust to the client screen size. This will allow you to have processes that will work for users using the standard 21-row window as well as those set up to use 28 rows.
As you migrate your users to the Appx Desktop Client, you will find that one advantage you gain is the ability to run APPX with a larger display area to take advantage of larger screens. We have found that using a display with 28 columns and 110 rows creates a nice screen size for 17” monitors running at a resolution of 1024x768. The screen is clear and readable and fits nicely in the display area of the monitor, plus it adds a good bit of extra room for your design needs.
So, how do you change the client’s default size? What other considerations need to be taken into account, and how can you avoid pitfalls, problems, confusion, and complaints?
Read what other users have said about this page or add your own comments.