APPX 4.2 release notes
Release notes for APPX 4.2.0 through 4.2.a, newest first. They were published on www.appx.com and moved here in October 2026. To move between releases, see Upgrade paths. Every release is listed in the Release history.Releases on this page
APPX 4.2.a
The APPX 4.2.a Patch Release fixes more than 140 previously reported bugs, listed below. For additional details, click on the bug for a link to the corresponding bug report.
Microsoft, Windows, Windows Server, Windows 2000, Windows Server 2000, Windows Server 2003, Windows 98, Windows NT 4, Internet Explorer, Windows Vista, Windows XP, Windows 7, Microsoft SQL Server, Microsoft Access and Microsoft Excel are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
APPX 4.2.9
The APPX 4.2.9 Patch Release addresses the following items:
- Bug #1761: Memory leak in RDBMS READ operations
- Bug #1811: Missing ODB Lock error
- Bug #1812: ILF Editor throws error incorrectly
- Bug #1824: Internal Error when PrintOnScreen Disposition cancelled
- Bug #1831: Disposition not honored when printing to client
- Bug #1832: FLEP on memory file interferes with scrolling input process
SPECIAL NOTE: APPX Release 4.2.8 and those that follow include the new 0AI (Application Installer) application. It is designed to support automated installation of the Open Source Business Applications. Existing customers currently have no need for application 0AI and can safely ignore it.
Bug #1761: Memory leak in RDBMS READ operations
- This bug was previously reported as fixed, but additional symptoms had surfaced.
- Those symptoms have been fixed in 4.2.9.
Bug #1811: Missing ODB Lock error
- APPX was still erroneously looking for the ODB product license when attempting to connect to SQL Server.
- Fixed for 4.2.9.
Bug #1812: ILF Editor throws error incorrectly
- If you have a field name where the file name portion was longer than 6 characters, and you tried to make it the target of a CNV TEXT field where the source is a date field, the ILF editor will complain with 'Error - Alpha Field Type Required'.
- Fixed for 4.2.9.
Bug #1824: Internal Error when PrintOnScreen Disposition cancelled
- An 'Internal Error Has Occurred' message appeared if you printed a PDF report (Print On Screen = Y) and then canceled the PrintOnScreen disposition input process.
- This is the same as Bugs #1189 and #1800.
- Fixed for 4.2.9.
Bug #1831: Disposition not honored when printing to client
- When local printing through the client is selected, the print disposition of SAVE does not save the print file in the PRINT/USR directory on the server. The file is deleted.
- Fixed for 4.2.9.
Bug #1832: FLEP on memory file interferes with scrolling input process
- If you define a File Level Event Point on a memory file and then use that memory file as the PCF of a scrolling input process, the input process can get wacked. The symptom varies, but after adding a record, the input process will probably display some sort of nonsense (illegal values).
- Fixed for 4.2.9.
APPX 4.2.8
The APPX 4.2.8 Patch Release addresses the following items:
- Bug #1079: Overriding LOGIC field as BIT field doesn't work
- Bug #1144: Temp filenames not guaranteed unique under Windows®
- Bug #1286: Fields modifiable in Inquire Mode
- Bug #1484: Can't enter Euro symbol
- Bug #1494: Input items with Modifiable=? behave strangely
- Bug #1554: ILF Editor TOO Smart when APPENDING
- Bug #1666: --- CLEAR PASS LIST steps on --- TEMP 80
- Bug #1667: 4.2.7 Java Client hangs when Incorrect Password entered
- Bug #1673: APPX error when converting an SQL Server® datetime field
- Bug #1676: Justification in Java client
- Bug #1689: pos() - invalid curs_reg message reported
- Bug #1701: Application-only optional children can cause crash
- Bug #1702: RECEIVE of a group header can cause crash
- Bug #1703: NULL DATETIME field can confuse ODBC interface
- Bug #1705: Bad RECEIVE and LOCAL statements compile without error
- Bug #1751: PRINTER file does not allow duplicate System ID's
- Bug #1758: Title bar does not display at runtime if rows > 21
- Bug #1760: Memory leak in BEG/END READ loop
- Bug #1761: Memory leak in RDBMS READ operations
- Bug #1763: ERROR statements don't appear on Action Logs
- Bug #1765: Cannot selectitemswhen>21 rows
- Bug #1769: Reportwriter doesn't honor runtime record selection changes
- Bug #1770: Reportwriter crashes when editing WHERE clause
- Bug #1781: Reportwriter 'Paste' doesn't work
- Bug #1782: Reportwriter 'Insert Char' doesn't work
- Bug #1783: Reportwriter buttons not right
- Bug #1786: ReportWriter problem choosing table for New Query
- Bug #1787: ReportWriter tutorial for Where is incorrect
- Bug #1846: CASSERT Message - 'Wrong Calling Convention'
- ECR #1790, 2342, 2549, et al: Output processes generate extra line feed
- ECR #4144, 4330, 4534, 4609, et al: Orphan sessions remain on server
SPECIAL NOTE: APPX 4.2.8 includes the new 0AI (Application Installer) application. It is designed to support automated installation of the Open Source Business Applications. Existing customers currently have no need for application 0AI and can safely ignore it.
Bug #1079: Overriding LOGIC field as BIT field doesn't work
- When overriding the LOGIC fields to BIT data type a problem is detected with the inputs. The Checkboxes always appeared UNCHECKED (if seen from the Java Client) and when checked the values don't seem to work properly in SQL Server. Leaving the fields as varchar(1) is the best method to handle this error.
- Initially reported fixed in 4.2.4, it appears that the fix for this bug broke LOGIC fields in existing SQL Server tables. You should have been able to override the data type for a LOGIC field from its (new) default of BIT to CHAR(1). But, the rsod.c conversion routines didn't seem to handle CHAR(1) fields.
- Fixed for 4.2.8 - you should be able to store a LOGIC field in a BIT column, a CHAR column or a VARCHAR column (maybe even a numeric or integer column).
Bug #1144: Temp filenames not guaranteed unique under Windows
- The APPX file manager was not generating guaranteed-unique file names (for temporary files) on Windows hosts. Namespace collision is unlikely in most cases because the file manager will create a new temporary file whenever a CREATE statement executes - it keeps trying until it finds a temporary file name that is not already in use. But, that makes it impossible to close and re-open a temporary file (which one would you re-open?).
- On Linux/Unix hosts, the file manager includes the file scope and process ID in the temporary file name. We should use the same naming method on Windows hosts.
- (Historical note - old Windows systems had an 8 character filename limit; the file manager is stripping off the unique identifier to force temporary file names to be no more than 8 characters long. Since we don't support 8.3 file systems, we can remove this limitation and use longer file names).
- Fixed in 4.2.8.
Bug #1286: Fields modifiable in Inquire Mode
- If you're in Initial Setup or Recovery Processing, any field with Modifiable = ? can be modified in Inquire mode.
- If you're in LIVE OPERATIONS in DELETE MODE, an item that has 'Modifiable?' set to blank is modifiable (it should not be), just like in INQUIRE mode.
- If you're in LIVE OPERATIONS in KEY ENTRY an item that has 'Modifiable?' set to blank is non-modifiable (it should be modifiable if part of the current key path).
- Fixed for 4.2.8
Bug #1484: Can't enter Euro symbol
- Can't enter the Euro symbol using the Java Client. It looks ok when you enter it, but after saving the data & recalling the record, it's replaced by a box character.
- Fixed for 4.2.8
Bug #1494: Input items with Modifiable=? behave strangely
- Items with Modifiable set to '?' are outlined inappropriately on the Key Entry screen. In Live Operations they appear with the normal screen background color but in Initial Setup or Recovery Processing they appear as though they were part of the key, although they are not open for input and you cannot tab to them.
- In Add or Change mode in IS/RP, they are open for input as they should be but a date field does not behave properly. You have to enter the slashes for the date to be formatted right. Also, as reported in Bug #1286, they are erroneously open for input in Inquire mode.
- All of the above behavior applies if the items have GUI attributes (control RAW TEXT or CALENDAR/CLOCK for the date field). However, if the items are defined without GUI attributes, the Key Entry screen appears fine in LO and the items are not open for input in IS/RP in Inquire mode. Other than that, the rest of the problems remain.
- Fixed for 4.2.8
Bug #1554: ILF Editor TOO Smart when APPENDING
- User wanted to APPEND to --- WIDGET a product number. When scanning, the desired field did not appear: SIC CUSTPNR1 PRODUCT NO is a domain X(18).
The field points to domain SIC SSY SAMEAS PRODUCT NO. SIC Domain is a SAME AS pointing to SSY SAMEAS PRODUCT NO. SSY Domain SAMEAS PRODUCT NO is an Alpha 18. Apparently, the link to the alpha field is too long and tenuous for the ILF editor to trace back. - Fixed for 4.2.8
Bug #1666: --- CLEAR PASS LIST steps on --- TEMP 80
- Apparently also --- STREAM BUFFER, --- TEMP 32K.
- Context was where --- CLEAR PASS LIST in a Post-PCF Read FLEP was stepping on the values set in the parent process.
- Fixed in the 0-apps for release 4.2.8
Bug #1667: 4.2.7 Java Client hangs when Incorrect Password entered
- If a bad password is entered, the Java client sucks up 50% CPU and does not return an error
- Fixed in the Java Client code for release 4.2.8
Bug #1673: Appx error when converting an SQL Server datetime field
- Appx throws an error (which causes a stack dump and causes the current process to abort) when it tries to convert a SQL Server date/time field into Appx format
- Fixed for 4.2.8.p4 (preview 4)
Bug #1676: Justification in Java client
- The Java Client seems to justify fields differently than it did before, in situations where an alpha field contains more text than can be shown in the area on the image.
- It used to always left justify the fields, so you always saw the beginning of the field. Now it seems to right justify the field, so you always see the end of the field, until you move to that particular record in change mode. Then it switches the justification to left.
- Fixed for release 4.2.8 in the client JAR file.
Bug #1689: pos() - invalid curs_reg message reported
- If you move the cursor off of all logical regions and press ENTER, a subsequent POSITION statement will get confused (because there is no active region) and you'll get the message mentioned in the title of this bug report.
- Fixed for 4.2.8
Bug #1701: Application-only optional children can cause crash
- When you invoke an optional child that specifies only a process type (MENU) and an application ID, Appx invokes the startup menu for the (current operational phase) for the given application.
- That confuses the menu/widget processor and can cause memory corruption (because the engine finds more optional children than widgets).
- Fixed for 4.2.8
Bug #1702: RECEIVE of a group header can cause crash
- When you execute a RECEIVE command and the source and destination operands are not of identical type, the engine creates a compiles a dynamic event point (at run time). If either operand is a GROUP HEADER field, the compiler can gag because it doesn't know the proper application version.
- Fixed for 4.2.8
Bug #1703: NULL DATETIME field can confuse ODBC interface
- A NULL DATE, TIME, or DATETIME value can confuse the Appx/ODBC interface causing a stack dump on Windows hosts. This is only an issue with release 4.2.6 and 4.2.7
- Fixed for 4.2.8
Bug #1705: Bad RECEIVE and LOCAL statements compile without error
- If you enter a RECEIVE or LOCAL statement that refers to a non-existent field (or you delete a field referenced by a RECEIVE or LOCAL statement), the process compiler will silently ignore the error but will throw an error at run-time.
- Fixed for 4.2.8
Bug #1751: PRINTER file does not allow duplicate System ID's
- The PRINTER file in System Administration does not allow two printers to have the same value for the 'system ID'.
- Changed the key from Unique Alternate to Alternate with Duplicates Allowed
Bug #1758: Title bar does not display at runtime if rows > 21
- In a simple scrolling input, with the size of the detail frame as '-2', use Window Properties to put a title in the header frame. Run in a standard 21 x 80 window, and all is good. Change row size of the client to 28 or 30 rows, and window title does not show at runtime.
- Fixed for 4.2.8
Bug #1760: Memory leak in BEG/END READ loop
- Each execution of a BEG/END READ loop (not each iteration, but each complete execution) leaks a small amount of memory.
- Fixed for 4.2.8
Bug #1761: Memory leak in RDBMS READ operations
- When you execute a READ statement (or a keyed PCF read) against a file stored in an RDBMS, the engine leaks a small amount of memory (the query chain should be discarded at the end of the read).
- Fixed for SQL-Server in 4.2.8.
Bug #1763: ERROR statements don't appear on Action Logs
- If you run a job with a query that selects records within only one range, and you have ERROR statements executed in a RANGE END frame of an UPDATE, then those ERRORs will not show on the action log. If the data is such that the RANGE-END frame would execute twice, then the first execution will show on the log, but the second will not. It seems as if ERRORs that are executed during the last execution of the RANGE-END frame do not appear on the Action log.
- Fixed for 4.2.8
Bug #1769: Reportwriter doesn't honor runtime record selection changes
- If you edit the record selection criteria of a query at runtime, the changes are ignored. The query is run using the record selection criteria as designed.
- Fixed for 4.2.8
Bug #1770: Reportwriter crashes when editing WHERE clause
- Reportwriter crashed when trying to edit a WHERE constraint. This happens when you are on the constraint screen for the second time.
- Fixed for 4.2.8
Bug #1781: Reportwriter 'Paste' doesn't work
- The paste option always reports that nothing has been cut even though a field has been cut.
- Fixed for 4.2.8
Bug #1782: Reportwriter 'Insert Char' doesn't work
- The insert character button does not shift fields correctly. It always seems to insert the space at the beginning of the row.
- Fixed for 4.2.8
Bug #1783: Reportwriter buttons not right
- The Ins/Del Char and the Ins/Del Row buttons do not look right. They are auto-GUI buttons and they do not fully cover the underlying text.
- Fixed for 4.2.8
Bug #1786: ReportWriter problem choosing table for New Query
-
The sequence of events is this.
- 1. After choosing an application for a new query, I got the tutorial for choosing a new table.
- 2. After pressing return to get past the tutorial, I got the list of tables but the arrow keys wouldn't work so I clicked on Customers.
- 3. However, the next tutorial described the A/P Receipts table.
- 4. When I cancelled, I got the screen asking for the report title for the A/P Receipts table.
- 5. When I cancelled that, I returned to the menu and selected New Query. Then I got the tutorial for designing a new query on the selected table.
- 6. After selecting Select, I got the message 'Unable to Locate Process'.
- 7. After cancelling, I got an 'Error - Record Not in File' message.
- FYI, this whole unhappy sequence of events can be circumvented at step 2 by pressing NEXT or PREV to wake up the table selection process. However, it does seem like there should be a graceful way to back up if you inadvertently select the wrong table.
- Fixed for 4.2.8
Bug #1787: ReportWriter tutorial for Where is incorrect
- The tutorial states that only columns that have been selected using the Select operation are displayed. However, all columns in the table are actually displayed and seem to work OK in Where clauses.
- Fixed for 4.2.8
Bug #1846: CASSERT Message: 'Wrong Calling Convention'
- Using the CALL statement to invoke a function in a Windows environment sometimes results in a CASSERT: 'You've CALL'ed C:WINDOWSSYSTEM32kernel32.dll,xxxxx with the wrong calling convention' where 'xxxxx' is the function being called.
- This is related to ECR 5376, and perhaps to ECR 4762 and others. The CASSERT message, which was added in 4.2.8, indicates that Appx has called a subroutine with an incorrect calling convention.
- Windows supports a number of different 'calling conventions', or rules for calling a function, and most of the kernel32 routines use a non-standard convention - there's no way for Appx to know in advance which convention to use. If the designer guesses the wrong one, the CALL statement could result in memory corruption. Thus, the CASSERT is now generated, to advise the designer of the problem. At the same time, APPX attempts to fix the problem itself.
- Windows supports two different (and incompatible) 'calling conventions' - __stdcall and __cdecl. By default, most applications (including Appx) use the __cdecl calling convention. When you invoke a function that uses the __cdecl calling convention, the caller (that's Appx) pops arguments off the top of the runtime stack when the function ends. When you invoke a function that uses the __stdcall convention, that function cleans its own arguments off of the top of the runtime stack before it returns to the caller. Appx can't tell the difference between __cdecl and __stdcall functions. Appx assumes (unless you tell it otherwise) that you want to call __cdecl functions. If you invoke a __stdcall function (and you don't tell Appx that you're calling a __stdcall function), the runtime stack will be corrupted.
- APPX tries to recover from this error but will also display a CASSERT message that tells you that you've CALL'ed a function with the wrong convention (the message includes the name of the function that you've called). If you see that message, add a '@' to the end of the function name (or, if you already have a '@' at the end of the function name, remove it). The '@' is the 'windows way' to tell Appx to use the __stdcall convention to call your function. For example, you currently invoke the Kernel32,DeleteFileA - change that to Kernel32,DeleteFile@.
- So how can you tell which functions are __stdcall and which functions are __cdecl? That's not an easy question to answer - that information is included with the Microsoft® C compiler, but I don't see it anywhere else. That's why APPX is displaying the CASSERT message here; so you'll know when you run into a problem. In general, most of the functions that you find in Kernel32.dll will be __stdcall functions (so you need to add an @ to the end of each Kernel32.dll function name).
- This issue is also addressed in the APPX FAQ system: http://faq.appx.com/cgi-bin/fom.cgi?file=592
- To learn more about calling conventions: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/_core_Calling_Conventions_Topics.asp
ECR #1790, 2342, 2549, et al: Output processes generate extra line feed
- There had long been an extraneous new line character (n) at the beginning of each page of an output. This caused the first page of a report to have one line less than it should have had, and resulted in alignment problems.
- The extraneous n has now been removed. Additionally, all form feed characters will now be preceded by a carriage return (r f).
- These changes may cause problems for installations that utilized work-arounds to deal with this long-standing issue. For those who would rather retain the old behavior, as opposed to reworking many output processes, a new environment variable has been created. By defining APPX_427_PRINT_FILES, the old behavior will be maintained.
ECR #4144, 4330, 4534, 4609, et al: Orphan sessions remain on server
- Appxd and appxdsvc.exe have been "fixed" so that an APPX session can more reliably detect that the TCP connection to the client has been lost. This means that the session can then terminate itself instead of hanging around indefinitely as an orphan. There are four environment variables that can be set to override the default settings for appxd. The configuration parameters for the Windows based APPXDSVC service can be specified in the registry. After the service is installed, you would add an Expandable String Value to the Config Key. The Config Key for the APPXDSVC service would normally be found at: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesappxd-8060Config
-
Configuration parameters for appxdsvce:
- # TCPEnableKeepAlive = true #Enable TCP dead-connection detection
- # TCPKeepCount = 8 #Maximum number of keep-alive pings
- # TCPKeepIdle = 300 #Idle time before ping sent to client (in seconds)
- # TCPKeepInterval = 60 #Interval between keep-alive pings
- # TCPNoDelay = true #disable TCP packet filling delay?
-
Environment variables for appxd:
- APPXD_DISABLE_KEEPALIVE
- APPXD_KEEPIDLE
- APPXD_KEEPINTERVAL
- APPXD_KEEPCOUNT
Microsoft, Windows, Windows Server, Windows Server 2000, Windows Server 2003, Windows Vista, Windows XP, Windows 7, Microsoft SQL Server and Microsoft Access are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
APPX 4.2.7
The APPX 4.2.7 Patch Release addresses the following items:
- Bug #539: XCOPY across applications still confuses ILF EDITOR
- Bug #1196: Restructure on RS/6000 destroys Data Files as soon as DD has FLEP's
- Bug #1305: Query fails to select any records on Descending key
- Bug #1328: APPX Can't Create files in Access
- Bug #1415: SET TOT gets wrong answer
- Bug #1485: uappxd does not honor startup process options
- Bug #1496: ILF editor loses position and statements
- Bug #1501: @ in Tooltip or Text doesn't work
- Bug #1512: ILF Editor can silently rearrange code
- Bug #1513: Automatic subtotals may overlap (PDF)
- Bug #1519: Query Fails to select any records
- Bug #1525: CNV PORT fails with fields longer than 256 bytes
- Bug #1530: Simultaneous access to the same resource
- Bug #1531: FLEPs are lost when applying a patch
- Bug #1549: RECEIVE statement can step on PASSED values
- Bug #1557: C-assert processing DD Runtime
- Bug #1585: Tooltips don't translate
- Bug #1586: Pulldown menu names are not being properly translated at runtime
- Bug #1590: Regular Expression memory leak
- Bug #1593: Appx can't create Oracle table with more than 512 columns
- Bug #1594: Lock held too long for query-constrained PCF stored in an RDBMS
- Bug #1596: Appx won't read record content in locked Oracle record
- Bug #1600: TRANSLATE subroutine doesn't work
- Bug #1601: TRANSLATE FIELD needs better error checking
- Bug #1602: In Progress messages are not being translated
- Bug #1608: Transfer query does not allow User ID with trailing spaces
- Bug #1611: Switching between cache and disk PCF can produce invalid record length CASSERT error
- Bug #1614: DB2 query optimizer seems brain damaged
- Bug #1615: DB2 on AS/400 reports unrecognized RDBMS name
- Bug #1626: Two-level input (with memory-file PCF at both levels) wonks out
- Bug #1627: Command line switches are broken in AppxDsvc
- Bug #1628: DB2 reports 'string representation of a datetime value'
- Bug #1630: License Usage PID field too small
- Bug #1638: Unable to translate message message is useless
- Bug #1659: PASS statement copies too much/too little data when passing a FILE
Bug #539: XCOPY across applications still confuses ILF EDITOR
- XCOPY from application BBB into AAA and all statements added have application ID defaulted to BBB.
Bug #1196: Restructure on RS/6000 destroys Data Files as soon as DD has FLEP's
- As soon as a file which has FLEP's wants to restructure the restructure utility reports errors. Afterwards the data file is empty.
Bug #1305: Query fails to select any records on Descending key
- If you have an alpha field that allows trailing blanks, and it's a descending key, and you try to run a query that uses that key field, and the criteria is EQ, and the criteria does not use every character of the field, the query will not select any records.
Bug #1328: APPX Can't Create files in Access
- Local APPX can create tables in Microsoft Access®, but Remote APPX (via appxdsvc.exe tcpip) cannot.
- Adding the environment variable to either the tail end of the appxdsvc.exe installation option, or to the appx.env file seems to fix this.
- This has been fixed for 4.2.7. AppxDSvc takes care of expanding the environment variables read from the registry and that translates the TMP (or TEMP) variable as needed.
Bug #1415: SET TOT gets wrong answer
- Occasionally, APPX will get confused and return the wrong contents after a SET TOT comand.
Bug #1485: uappxd does not honor startup process options
- The uappxd connection manager does not honor startup process options when they are specified on the java client command line.
Bug #1496: ILF editor loses position and statements
- The ILF editor will often lose its current line position when adding or moving statements near the end of the event point. This results in statements being inserted in the wrong position, statements appearing to be duplicated, and even statements being deleted without warning.
Bug #1501: @ in Tooltip or Text doesn't work
- If you put an '@' in a tooltip or in the text of a label, nothing after the '@' is displayed to the user.
Bug #1512: ILF Editor can silently rearrange code
- Related to #1496, but scenario was at top of event point, rather than at end.
Bug #1513: Automatic subtotals may overlap (PDF)
- When automatic subtotals are created by APPX for fields that are being totaled, subtotal fields may overlap if fields that are being totaled overlap from multiple rows, images, or frames.
- This problem only exists when PDF output is requested.
Bug #1519: Query Fails to select any records
- If you have a key field > 22 bytes long and you use it in a query, it will not select the proper records.
- Query processes have always limited literal values to 30 characters or less. When range-read optimizations were added a while back, the query processor was damaged so that literal values were limited to 22 characters (or less). To fix this bug, the limit has been restored to 30 characters.
- NOTE #1 - Increasing that limit beyond 30 is considered an enhancement request.
- NOTE #2 - Key values with a length of 22 or less result in a constrained read of the PCF. Key values longer than 22 characters result in an unconstrained read of the PCF.
Bug #1525: CNV PORT fails with fields longer than 256 bytes
- A CNV PORT statement fails if the destination (alpha) field is longer than 256 bytes. If the source field is a numeric field, the CNV PORT causes a seg. fault. If the source field is a date field, the CNV PORT fails (but correctly returns a 'F').
- Definition of statement: "CNV PORT works like CNV TEXT except that the portable format is designed for import/export purposes and is immune to differences in numeric and date masks. CNV PORT ensures that you can import anything that you export."
Bug #1530: Simultaneous access to the same resource
- The resource record is held causing a cassert if another user attempts to use the same resource.
Bug #1531: FLEPs are lost when applying a patch
- It appears that APPX does not copy FLEPs when transferring a file definition using the Design Transfer - All utility. Furthermore, there is no warning given that this has happened, either on the screen or in the transfer log. This would be fine, except for the fact that existing FLEPs are deleted when the file definition is subsequently applied as a patch, again without warning.
- Design transfer has been modified so that it always transfers the Flie Level Event Points (FLEPs). The text of the warning has been altered so that instead of stating the FLEPs will not be transfered if the App ID or Filename is changed, it states that in this case the FLEPs will be transfered but the code should be revised manually to correct App ID and Filename changes.
- NOTE: We do not automatically try to convert the App ID or Filename in the FLEP code because you may be using the destination applications as a temporary holding area to copy code from development into production. And chances are that if you are really crossing into a new app ID or new filename you will need to make other alterations to the code beyond just changing the App ID and File name on the statements related to this file.
Bug #1549: RECEIVE statement can step on PASSED values
- A RECEIVE statement in a subroutine that references a field name that is also referenced by a PASS statement in the calling process that has not yet been received will modify the value of the yet to be received field. This will cause the wrong value to be received when a subsequent RECEIVE statement is executed.
Bug #1557: C-assert processing DD Runtime
- Fixed for 4.2.7.
Bug #1585: Tooltips don't translate
- Tooltips are not being tranlated at runtime. It appears that the engine is using the wrong length for the tooltip field. The tooltip field has a length of 60. The engine appears to be using a length of 256.
- The tooltip is being added to the translation dictionary with a length of 256. Positions 61-256 contain 'garbage'.
Bug #1586: Pulldown menu names are not being properly translated at runtime
- The 'WIDGET GROUP NAME' field is not currently being tranlated. The 'WIDGET LABEL' field is being translated. As a result, pull-down menu items and sub-menu items are not being associated with the correct pull-down menu groups.
Bug #1590: Regular Expression memory leak
- Every time you use the Appx regular expression matching relational operators, memory is allocated and never freed until you exit the session. Usually several K each time. The amount of memory consumed each time is larger with a more complex expression.
Bug #1593: Appx can't create Oracle table with more than 512 columns
- If you try to create (or open) an Oracle table that contains more than 512 columns, Appx crashes
Bug #1594: Lock held too long for query-constrained PCF stored in an RDBMS
- The record lock held for the last record in a query-built result set is held too long if the PCF record is stored in an RDBMS.
Bug #1596: Appx won't read record content in locked Oracle record
- When Appx encounters a locked record in an Oracle database, it may not read the record content (leaving the wrong data in the record buffer). This only occurs when the engine re-reads a locked record by its record-ID.
- Also fixed for DB2 and ODBC
Bug #1600: TRANSLATE subroutine doesn't work
- The 0LA TRANSLATE subroutine does not correctly identify the Application and Version.
- NOTE: This subroutine has not yet been released for general use.
Bug #1601: TRANSLATE FIELD needs better error checking
-
The 0LA TRANSLATE FIELD subroutine needs to check for and gracefully handle:
1) A blank source string.
2) The from and to language ID's are the same.
Neither of these conditions should occur but they do. The subroutine needs to anticipate that the conditions might occur and handle them without crashing. - The subroutine will now return a blank field when passed a blank field.
- The subroutine will now return the original text when the from and to language IDs are the same.
Bug #1602: In Progress messages are not being translated
- When running an application with a language ID set, the In Progress message for a Job is not being translated.
Bug #1608: Transfer query does not allow User ID with trailing spaces
- The transfer query utility displays a 'Blank not allowed' message if either of the User ID fields contain trailing spaces.
Bug #1611: Switching between cache and disk PCF can produce invalid record length CASSERT error
- In an input process whose PCF is a disk file, scan against a cached version of the PCF. When you come back from the scan and change modes, you'll get an invalid record length CASSERT error.
Bug #1614: DB2 query optimizer seems brain damaged
-
Customer reported that it takes a long time (anywhere from 6 to 40 minutes)
for an input process to start when using a particular DB2 table. The
table has 35 million records and occupies 4+ gigs on the AS/400. -
They turned on logging, and noticed line 'Select * from auliv61f.tttb
where 1 = 0' in the log. They monitored the sql log while APPX was
connecting, and the pause occurred when this line was executed. For
confirmation, they logged on directly to DB2 and entered the command,
and it took 6 minutes to run there as well. - Fixed (hopefully) for 4.2.7, but you must set APPX_USE_SQLCOLUMNS to force Appx to use an alternate method to retreive the metadata for a table.
Bug #1615: DB2 on AS/400 reports unrecognized RDBMS name
- A DB2 instance running on an AS/400 host reports an unrecognized RDBMS name (AS). On all other hosts, DB2 reports 'DB2'. The Appx/DB2 interface treats DB2 on an AS/400 as a generic RDBMS of unknown type.
Bug #1626: Two-level input (with memory-file PCF at both levels) wonks out
- If you have a multi-level input process family (with auto-update of the child PCF) and the parent and child PCF's are both memory files, Appx will crash when you delete a record at the parent level.
Bug #1627: Command line switches are broken in AppxDsvc
- Using AppxDsvc services and trying to launch Appx from the client using the command line switches like -runApplication, -runDatabase, -runProcess and -runProcessType, they will not be honored. They do, however, work for WinAppxD.
Bug #1628: DB2 reports 'string representation of a datetime value'
- If you try to store a CCYYMMDD field in a DB2 database, you'll get an error that states ' string representation of a datetime value '
Bug #1630: License Usage PID field too small
- The License Usage field 'PID' on the System Registration is too small. It shows ???? for PID's greater than 99,990. AIX 5.2 is assigning PIDs that are 7 digits.
- Expanded PID field on scrolling screen and reworked screen to be bigger so more scrolling records can be viewed at a time
Bug #1638: Unable to translate message message is useless
- An 'unable to translate message' error occurs when the Appx runtime tries to convert an error code (as defined in the 0LA message file and la.h) into a human-readable, localized form. In almost every case, the error occurs because the engine has reported an error whose code does not appear in the 0LA MESSAGE file (that should never happen). To aid in debugging this sort of problem, we should remove the extra information displayed in that message (because it's confusing) and replace it with the raw error code and the runtime (engine) context.
Bug #1659: PASS statement copies too much/too little data when passing a FILE
- When you PASS a FILE (to a CALL, RUN, or RECEIVE statement), the PASS statement typically copies too much or too little data to the receiving field. It may also copy too much/little data when restoring the field value on return.
- This can cause memory corruption and may explain some/all of the exceptions thrown by the NSCAN process
Microsoft, Windows, Windows Server, Windows Server 2000, Windows Server 2003, Windows Vista, Windows XP, Windows 7, Microsoft SQL Server and Microsoft Access are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
APPX 4.2.6
The APPX 4.2.6 Patch Release addresses the following items:
- Bug #1424: AT FIELD statement can be added in invalid Event Points
- Bug #1426: Export/Import Application to a Single-File fails
- Bug #1444: Changing Named Resource fails to build new EM
- Bug #1445: Java Client does not always detect server resource changes
- Bug #1448: Widget Sync utility must be required on upgrade
- Bug #1451: APPX_PRT_SCRIPT skipped when PRINT MODE=HOLD
- Bug #1476: Java Client slow over low bandwidth connections
Bug #1424: AT FIELD statement can be added in invalid Event Points
- AT FIELD statements are only valid in Option Intercept and Global Option Intercept. A designer should get a 'Warning - This statement has no effect in this event point' message if you add it elsewhere. The warning did appear in non-image event points, but not in Pre-Display, Pre-Display/Verify, or Verify.
- This has been fixed in 4.2.6 to display the warning in all invalid event points.
Bug #1426: Export/Import Application to a Single-File fails
- When exporting an application to a Single-File (e.g. for transfer from Linux to AIX) the application could not be imported back. The import silently ended within 1-2 seconds and has NOT imported the application.
- This has been fixed for 4.2.6.
Bug #1444: Changing Named Resource fails to build new EM
- Changing a Named Resource record did not cause any related EMs to be rebuilt.
- This has been corrected for 4.2.6.
Bug #1445: Java Client does not always detect server resource changes
- The java client did not always detect that a server-side resource had changed and needed to be re-cached.
- Client detection and cache clearing of server side resources that have changed has been tightened for 4.2.6 to resolve this problem.
Bug #1448: Widget Sync utility must be required on upgrade
- In prior releases, the designer would be prompted to run the Widget Sync utility when it detected an application with old widget records. The designer had the option to skip running it and continue designing. If the designer opted not to run the utility and did some design work, then later tried to run the utility, it would fail since some of the fields it needs to update were already filled in.
- This has been changed to prevent access to application design in 4.2.6 if the Widget Sync utility has not been run.
Bug #1451: APPX_PRT_SCRIPT skipped when PRINT MODE=HOLD
- APPX was not invoking the APPX_PRT_SCRIPT (or any script) when a PDF report was spooled with PRINT MODE = HOLD. APPX did invoke APPX_PRT_SCRIPT when spooling a text report with PRINT MODE = HOLD.
- This has been fixed in 4.2.6.
Bug #1476: Java Client slow over low bandwidth connections
- The java client was very slow over a 64K ISDN connection. This had gotten much worse with the 4.2 GUI application design screens.
- An inspection of the 4.2 client datastream found extra widget specifications being sent. Basically the pulldown menu widgets were being sent twice on a non-scrolling menu or input. On a scrolling input the pulldowm menu widgets were also sent again for each scrolling record in the screen. So, for example, viewing the scrolling list of input processes woud send 221 widgets instead of the 79 required. Eliminating this duplication dropped the raw data being sent for the input process scroller from 44K to 25K. This is fixed for the 4.2.6 engine release.
- NOTE: All GUI input and menu processes that have pull-down menus should benefit from this change.
APPX 4.2.5
The APPX 4.2.5 Patch Release addresses more than 320 previously reported bugs. They are divided into the categories listed below. Click on each category to review the related bugs. For additional detail on any bug, APPX resellers and supported customers may refer to the BugTracker System.
In addition to the categories, this release also contains one new feature ("Shrink to Fit Content" widget attribute) and one new known bug (PDF output doesn't support multiple appearance fields). Links to those items appear at the bottom of the list.
Important Notes Concerning Release 4.2.5
- Upgrading to APPX 4.2.5 from any prior release will require that you scratch and re-create the design structure files in all applications, and run the Sync Widget Elements utility thereafter. Refer to the Installation Instructions for further information.
- Single-file import/export, which worked in previous versions, is temporarily non-functional in APPX 4.2.5 (fixed in 4.2.6). Additionally, import/export should never be used across versions - exporting from a prior version and attempting to import into 4.2.5 is likely to result in severe data corruption.
- APPX 4.2.5 is the first release to include support of the HP Itanium processors. Files may be downloaded from the HP Download page.
- Please also note that blank line compression and float spaces are now fully functional in both PDF and text outputs.
APPX/Net (1 bug)
Connection Manager (3 bugs)
Database Management (1 bug)
Design - General (16 bugs)
Design - Cross Ref. (3 bugs)
Design - DD (3 bugs)
Design - ILF Editor (10 bugs)
Design - Image Editor (18 bugs)
Design - Processes (31 bugs)
Design - Tech Doc (5 bugs)
Design - Transfer (4 bugs)
Design - Utilities (4 bugs)
Design File Management (4 bugs)
DISAM (2 bugs)
Documentation - 0-Apps (4 bugs)
GUI - 0-Apps (1 bug)
ILF Interactive Debugger (2 bugs)
Install/Uninstall (1 bug)
Java Client (27 bugs)
Kit Build (3 bugs)
ODBC Interface (Windows®) (1 bug)
RDBMS Interfaces (2 bugs)
ReportWriter (SQL) (9 bugs)
Runtime - 0-Apps (15 bugs)
Runtime - APPX Engine (41 bugs)
Runtime - PDF Output (91 bugs)
Runtime - Proc Compiler (1 bug)
System Administration (8 bugs)
User interface (8 bugs)
Winprint (1 bug)
New Widget Attribute - Shrink to Fit Content
Known Bug - Appearances in PDF Output
APPX/Net (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to APPX/Net
Bug #1327: APPX/Net causes Bus Error - Itanium to Windows®
- When attempting to establish an APPX/Net connection between an Itanium system and a Windows system, a Bus error resulted.
- Fixed for 4.2.5.
Connection Manager (3 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Connection Manager
Bug #652: Appxdsvc command does not set environment variables
- When setting the APPX KEYMAP environment variable on the appxdsvc command line, it didn't appear to be honored.
- Seems OK in 4.2.5.
Bug #743: AppxdSvc Always Logs
- The new appxdsvc always seems to create log files in the root of c:. These are useful when starting off, but how can they be turned off before they fill the drive?
- The logging parameters can be adjusted by setting three registry values:
- LogServiceDir - set to the name of a directory and AppxDSvc will write the log there (in a file named $(LogServiceDir)serviceName.log
- LogAllEvents - set to 'Y' to get a complete log or any other value to disable most log messages. The default is 'N' so Jean should be seeing very few message written to the log
- LogCreate - set to 'Y' to create a log file or any other value to disable logging. The default is 'N' (starting with 4.2.3 - it defaulted to 'Y' before release 4.2.3)
- Fixed for 4.2.5.
- There are a few new installation parameters that let you control the location of the log file and the level of detail. Run appxdsvc /? for details.
- If you just type appxsvc at the command line, you should see a summary of the command line options:
- Usage:
- .AppxDSvc.exe -install <install-options>
- .AppxDSvc.exe -remove -name=serviceName
- .AppxDSvc.exe -status
- .AppxDSvc.exe -start [serviceName]
- .AppxDSvc.exe -stop [serviceName]
- INSTALL-OPTIONS
- -name=name defines the name of the service
- -displayName=name defines the display name for the service
- -port=port specifies which port the service will listen on
- -engine=path defines the complete name of the Appx engine
- -AM=method authentication method (see below)
- -logdir=directory default log file directory
- -log create a log file
- -log=pathname create a log and write it to given pathname
Bug #1229: Default TCPNoDelay to True
- The client was not setting the TCPNoDelay setting to true. This was slowing down communications between the client and the server.
- Fixed for 4.2.5 - The default value for TCPNoDelay is now 'True' for the client, appxd, winappxd, and appxdsvc.
Database Management (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to Database Management
Bug #885: Screens > 21 rows - Database Management
- When running with >21 rows, you get an ugly appearance as this process needs a box or a blanking frame.
- Fixed for 4.2.5 - Added a box. It now looks OK.
Design - General (16 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - General
Bug #11: Scrolling problem - records duplicated
- Scrolling screens sometimes displayed the same set of records twice.
- Fixed for 4.2.5 - Reviewed all CLOSE statements in 0AD and corrected the CLOSE statements that were the source of the problem. One side effect of this change is that APPX application design may now keep a few more files open.
Bug #462: Can't Opt 99 from drill down
- While examining a job, and using Opt 94 to drill down to the underlying process, trying to run that process via Opt 99 results in the error, 'Option Invalid whie editing from the process compiler function', even if it is not in the process compiler function.
- Fixed for 4.2.5 - processes may now be compiled and/or invoked after drilling down with option 94. However, processes may not be compiled and/or invoked after drilling down from compile errors.
Bug #463: Toolbox active but no Visual Cue
- The Option 1 toolbox (available in the DD and various points in process design) seemed to be available, but there was no GUI or other visual clue to let the designer know about it.
- The 'old' toolbox popup menu is no longer available when running with the GUI client. All items on this menu are now available from the new Toolbox pulldown menu.
- Side benefit is the Reference Browser is availbable even at the Frame / image level.
- Fixed for 4.2.5 - When running the GUI Client, the 'old' popup toolbox menus are no longer accessible as a hidden option from:
- Processes
- Frames
- Images
- Domains
- Files/Fields
- Work Fields
- Pull-down menus now provide access to the functions that were previously available on these popup toolbox menus.
- However, the old 'popup' toolboxs are still available from:
- ILF Editor
- Image Editor
- Item Editors
- because there are no pulldown menus defined at those points.
- The cross-reference utilities and the change all references utilities are now accessed by clicking on the 'Jump To - Application Design Tools' toolbar button or pull-down menu.
- Fixed in 4.2.5.
Bug #570: Lockout after viewing ILF in Inquire Mode
- If user #1 has an ILF series open in Change mode, and user #2 goes into any ILF series in the same Process in Inquire mode, when #2 attempts to exit viewing that series in Inquiry mode, it locked up, waiting for user #1 to release a Process-level hold.
- Fixed in 4.2.5.
Bug #712: Wrong abbreviation for ID
- The abbreviation for 'identification' or 'identifier' should be ID, all caps. It appeared as 'Id' on every screen in the Change All References family, and twice on the Tools menu. Ditto for 'Recalculate Hash IDs' on the Language menu.
- Fixed for 4.2.5.
Bug #764: Invoking process w/o database ID acts unexpectedly
- When trying to invoke a process, but neglecting to include a database ID for that process, it goes back to the main APPX menu. Hitting "Design an Application" from that menu results in an error, from which one cannot cancel out but have to end task. If at the main APPX menu you try to Exit APPX, it instead takes you back to the list of processes from which you had just tried to choose one to run.
- Fixed for 4.2.5 - An error is now displayed if you try to invoke a process without specifying a database ID.
Bug #809: Scan starts at original field name, not current field
- In design of outputs, when an item already exists, but the field name is to be changed, after typing in a different app and file name, then SCAN, the scan screen starts with the original file name, but within the new application just typed in.
- When scanning by field name, the scan is working OK. The problem exists only when the path to scan is file name and sequence number.
- Fixed for 4.2.5.
Bug #882: 0SA APPL ALLOW DESIGN - No longer works
- In 4.2.2 the new feature allowing changing of modes at lower levels now allows changes to the design as well at lower level dispite the setting of the 0SA APPL ALLOW DESIGN field.
- Fixed in 4.2.5. The application chooser now shows a READONLY icon in the left column of the scrolling display for applications that are locked from changes due to the Application 'Allow Design?' flag.
Bug #884: REFRESH TEMP 80 is broke
- In an Update that flashes a REFRESH TEMP 80 message, it no longer worked in a simple running of the process.
- Fixed in 4.2.3 - REFRESH appears to be working in all places.
Bug #1087: 0apps cursor in wrong place
- If you are adding records on a scrolling display, when you reached the bottom of the display and added a record, after returning to the scrolling display, the cursor was on the row above the bottom row.
- Fixed in 4.2.5.
Bug #1129: Duplicate keyboard shortcuts
- In Job Streams, the keyboard shortcut for Cancel and Child Constraint was the same, and Cancel took priority. When the designer pressed Alt-C to go to Child Constraints, they got cancelled instead.
- Duplicate shortcut removed for 4.2.5.
Bug #1142: Hot key duplicated in Application Design on Inquiry
- In Application Design the hot key for Automatic Children for the Inquiry process Frames entry was A, which is in conflict with Additional Attributes. If Alt-A is selected the Automaic Children option is executed. Alt-A should probably execute the Additional Attriibutes option.
- Fixed for 4.2.5. Alt-A calls Add'l Attributes and Alt-C calls Automatic Children.
Bug #1167: Default mode inconsistent
- Using the 1) Toolbox for the ILF editor, jumping to the Data Dictionary, APPX jumps to the 'old' application design screens. Also, the default mode on these maintenance screens is CHANGE, while the new screens are INQUIRE.
- Fixed for 4.2.5 - Domains, Files, & Work Fields are now always invoked in Inquire mode from the Database Management menu.
Bug #1171: Warning message on User Selections not clear
- When a field is added to End User Selections on a Query a warning is displayed that says: "Warning: Define Access To This Field In 'Before User Selection' Evnt Pnt". This does not match any of the event point names displayed under rules.
- Fixed for 4.2.5 - Changed message to refer to the correct event point. Also changed the corresponding message that is displayed when editing sort order records.
Bug #1226: Wrong DD processed after running FILES EDIT
- Processing the Data Dictionary after running the Files Edit utility would process the wrong files.
- Fixed for 4.2.5rc2
Bug #1371: Tool tip incorrect on Switch Apps button
- The Switch Apps button on the Application Design main menu reads 'Save the current record and edit the process frames'. It should instead refer to returning to choose an application.
- Fixed for 4.2.5, tooltip now reads 'Click to close this application and open another application'.
Design - Cross Ref. (3 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Cross Ref.
Bug #1016: Cross reference - Load All Applications is missing
- When running a cross reference on a Process, there used to be a button to 1) Add All Applications this Version. There was no such button any more.
- Fixed for 4.2.5 - Added missing button on bottom of window.
Bug #1017: Cross Refence - Applications to Search
- When running a cross reference and adding applications, selections from all versions were presented when scanning. But choosing an app from a version other than the current one resulted in an error - Invalid Application!
- Fixed for 4.2.5 - scan now lists only the applications in the current version.
- NOTE: Test was in version 15. Pressing Add and then F2 produced a list of only version 15 with the addition of 0AD 00, 0LA 00, 0LC 00, 0SA 00. The 0-app 00 versions were on the list and when selected still said Invalid Application.
Bug #1049: Field/Domain X-ref incomplete
- If you used the Field/Domain x-ref in the Domain Toolbox, it did not report other domains that are SAME AS the current domain.
- Fixed for 4.2.5 - The Domain cross-reference option has been removed from the domain toolbox.
- The domain cross-reference utility that was previously accessible from the toolbox menu in character mode is obsolete. The new cross-reference utility that can be accessed from the Tools menu offers additional functionality and includes the previously missing Domain references.
Design - DD (3 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - DD
Bug #14: DD changes are not always processed
- When you made changes in the Data Dictionary, it wasn't always processed when you exited.
- Fixed for 4.2.5.
Bug #1177: Initial Value problem with Logic Domains
- You could not specify an initial value for Logic Domains. You can enter it at the domain, but it was not honored when you used the Domain in a field.
- Fixed for 4.2.5 - The default value for a logic field that is defined by a domain now displays the default value from the domain record and is not modifiable.
Bug #1242: Domains maintenance needs work
- The domains maintenance screen needs to be updated to include the standard toolbar buttons and pulldown menus.
- Fixed for 4.2.5 - Pull-down menus and Toolbar buttons have been updated to be consistent with other design processes.
Design - ILF Editor (10 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - ILF Editor
Bug #410: Paste ILF Code
Bug #619: One-Rec File asking for Key
- The ILF Editor is Erroring on a: READ DOC PARAM ... Error - Enter field name or constant ... where PARAM is ONE-REC Permanent file.
- Fixed for 4.2.5.
Bug #647: Java Client - Pick Up and Put Down doesn't work in ILF editor
- 'Pick' up and 'put down' (ctrl-c and ctrl-v) did not appear to work in the ILF Editor.
- Fixed for 4.2.5.
Bug #873: Paste ILF code doesn't always work
- Deleted some ILF code from Pre-Display for one image and tried to paste it into Pre-Display for another image but, instead of pasting the code, it exited the event point when clicking Paste. Tried pasting into Start of Process and the same thing happened. Was able to successfully paste the same code into Pre-Display for another image without copying it again. Then tried the problem image and Start of Process again and both still refused to paste, just exiting the event point instead.
- Under APPX 4.2.5, consider this bug fixed now.
Bug #914: Scanning on field name too restrictive
- When scanning on the source field name of an APPEND statement, the scan list did not include ALPHA fields that are defined by DOMAINS.
- Fixed for 4.2.3.
Bug #951: XCOPY - Ugly Screen > 21 rows
- Another screen that looks bad when running with > 21 rows.
- Fixed for 4.2.5 - box now around XCOPY screen.
Bug #996: File Names not available to scan from READ stmt
- When entering a READ statement and scanning to select the file name to be read, only field names were presented, and the 'Select File' option button did not function.
- Fixed for 4.2.4 - When you scan on an operand that can contain a field name or a file name, you should now be able to scan for either. The scan processor should show you the list of files by default - use option 1 to scan fields instead. The scan processor will remember your scan preference.
Bug #1174: ILF Editor give bogus warning on GOSUB
- If you have a GOSUB the refers to a local label, and the app id is filled in, then the ILF editor will complain the subroutine does not exist.
- Fixed for 4.2.5
Bug #1178: Seg Fault in ILF Editor
- If you used F2 to select a key on a READ statement, you would be exited from the ILF editor without any warning & all changes were lost. If you persisted in doing this, APPX would seg fault.
- Fixed for 4.2.5.
Bug #1203: Pasting an invalid application ID causes ILF editor to crash
- Pasting a statement containing an invalid (e.g. unrecognized) application ID into the ILF editor caused the ILF editor to crash.
- Fixed for 4.2.5.
Design - Image Editor (18 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Image Editor
Bug #198: LABEL Icon Position display can vary with icon size
- On the Output image, using 24 pixel icons, each Icon Position produced an appropriate result. However, if you used 16 pixel icons, there was no distinction between Leading Text, Above & Leading, and Below & Leading and between Trailing Text, Above & Trailing, and Below & Trailing. Note that with the 24 pixel icons, it is actually changes in where the text displays that produces the differences in the result (even though the Text Position attribute is the same).
- This is how the Swing library implemented this feature. Internally in the swing library, it is really positioning the text relative to the icon, not the icon relative to the text. And the positioning is done solely based on the size of the icon and the text, not relative to the widget they are going to be drawn inside of. So, if the text and icon are very close to the same size, you will not see much difference.
- Considered fixed on the basis of accepting whatever the Swing library ordains in regard to this feature.
- Also, changed the Icon Position token list so that the descriptions better match the behavior. The text for the following four token values have been changed as noted below:
- ABOVE & TRAILING is now TRAILING BOTTOM ALIGN
- ABOVE & LEADING is now LEADING BOTTOM ALIGN
- BELOW & TRAILING is now TRAILING TOP ALIGN
- BELOW & LEADING is now LEADING TOP ALIGN
Bug #613: Touching field disappears
- If two fields in the image editor touched each other and you tried to move the second, the first was deleted immediately. Besided this it should be possible to place the fields without a space in between; at the moment it is not possible to move the second field next to the first one, but you can move the first one next to the second.
- Fixed for 4.2.5.
Bug #729: Show Object Bounds compresses spaces from row text
- If an image contains one or more lines with row text, clicking the icon to show object bounds would left-justify and compress spaces from one of the lines of row text - usually the first line but not always.
- Fixed under 4.2.5.
Bug #775: Image Editor Toolbox should use Optional Children terminology
- Now that the Optional Child Processes screen has been labeled Optional Children, it seems like the toolbox should use this designation as well, not Optional Processes.
- Fixed for 4.2.5.
Bug #778: Image Editor Toolbox Rules Option problem for Menu/Input
- When you use the Image Editor Toolbox Rules Option within a menu process, the buttons on the Event Points for Rules overlay were disabled. Within an input process, the buttons are enabled until you reach the Global Event Points overlay. Then those buttons are disabled.
- Fixed under APPX 4.2.5.
Bug #779: Image Editor Toolbox Rules Option problem for Inquiry
- Nothing happened when you invoked the Rules option from the Image Editor Toolbox within an inquiry process. The image was just redisplayed.
- Fixed for 4.2.5. This now behaves the same way as invoking the Toolbox from an output image (see Bug #780). In other words, if you are in Change mode on the image, you are switched to Inquire mode when you invoke the Toolbox. Unless you make a change to a rule, you stay in Inquire until you return to the image.
- When invoked via the image editor toolbox, the mode of the ILF editor is now set based on the original mode of the 'image' record. So, if you were in inquire mode when the image editor was invoked, the ILF editor will be invoked in inquire mode even though the mode of the image editor may have switched to change mode after it was invoked.
Bug #780: Image Editor Toolbox Rules Option problem for Output
- Weird things would happen when you invoked the Rules Option from the Image Editor Toolbox within an output process.
- Sometimes the Event Points for Rules overlay was a little strange. It could use Courier font and the buttons on the titlebar may not be recognizable. Then, when you returned to the image, row text on the image may be misplaced.
- On another image, the Event Points for Rules overlay looked fine but when you called up an event point, the buttons on the event point titlebar were unrecognizable.
- Fixed under 4.2.5.
Bug #781: APPX Data Palette does not list any items
- I would get the same results (empty data palette) regardless of what application or process I'm in.
- This was probably fixed a long time ago. Anyway, it works fine under APPX 4.2.5.
Bug #928: Field labels should default to Transparent=Y
- Ordinary label widgets default a 'Y' in the Transparent? field. Data items which are assigned a label widget default to 'N'. Unless there's some compelling reason why this is so, data labels should also default a 'Y' in the Transparent? field.
- Fixed for 4.2.5 - The value for 'Transparent BG' is now set to 'Y' anytime the control type for an Item widget is changed to be 'LABEL'.
Bug #954: Field label won't behave in IE
- Designing a PDF special form, printing fields as Labels with a border to simulate a box. Hence, stretching the borders of the field to abut the fields around it. Sometimes it works but in one particular case, the field won't go where it should. It keeps jumping down a row.
- Fixed for 4.2.5.
Bug #959: OIE deletes field, GUI attributes
- In an output process, the first line is regular label widgets and the second line is data label widgets. When attempting to abut one field to another, the field on the left is deleted from the image, along with all the GUI attributes. Also, it doesn't appear to be honoring the 'center' attribute, although all the other fields are.
- Fixed for 4.2.5.
Bug #979: Changing modes in GUI Attributes causes c-assert
- When entering GUI attributes for a field for the first time, APPX (logically) puts the user into ADD mode. But if the user switches to CHANGE mode, an attempt to save the record causes a c-assert error (record not on file) with no way to correct it.
- Fixed for 4.2.5 - The widget editor screens no longer allow mode changes.
Bug #1090: Java Scan on App ID in Image Editor
- On the image editor, adding a new field (output), pressing F2 on the App ID part of the field did not present any results
- Fixed for 4.2.5 - scanning on application ID is now constrained to display only the available applications.
Bug #1216: Unexpected error message in output process design
- Defining a label widget for a field on an output process image sometimes caused the following error message 'Label widget not valid for modifiable field'.
- Fixed for 4.2.5
Bug #1243: Can't remove all GUI attributes in Output process
- Attempted to remove all the GUI attributes from an Output process. The GUI attributes screen then appeared null, but the 'GUI Attributes' button was still highlighted. Printing the report gave some strange results, which are recorded under Bug #1187.
- Fixed for 4.2.5 - The Transparent attribute was not being reset to 'N' when the widget type was set to NULL. You can now extinguish the GUI attributes flag by removing all the GUI attributes.
Bug #1247: Text Area widgets should default Transparent = Y
- The Update Widgets process made all Text Area widgets into Transparent = Y. But if you edit a text field and assign a Text Area widget to it, it defaults to Transparent = N. It should default to Transparent = Y. (See related Bug #1149.)
- Fixed for 0-apps 4.2.5 - The default value for Transparent is now always NULL for all types of widgets. You should only need to change it to Y/N by exception.
Bug #1332: Icon Position value is truncated on Label Properties screen
- Now that the new token values for Icon Position (see Bug #198) have been implemented, the field size needs to be enlarged on the Label Properties screen. Otherwise, the value appears truncated with '. . .'.
- Fixed for 0-apps 4.2.5.
Bug #1380: Odd behavior after changing font for alpha label widget on output image
- Say you change the font on an alpha label widget and save it, then keep pressing F8 to end out of the output, when you reach the process level, the screen will be blank (instead of returning you to the next output process on the scrolling display). If you press Return on the blank screen, you will get an 'Error - File is Not Open' message. If you end all the way out and run a job containing that output, the job will not recognize that the output has been changed; i.e., the output will not be recompiled (you can also change row text at the same time you change the font and the behavior is the same).
- Fixed for 4.2.5.
Design - Processes (31 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Processes
Bug #302: New Page B4/After editable on PAGE-START & END?
- Concerning 'New Page B4' and 'New Page After' with regard to PAGE-START and PAGE-END Frames and Images: These parameters make no sense when applied to those two frame classes and these parameters should not be editable for those two frame classes, either at the Frame level or at the Image level.
- Fixed for 4.2.5 - Page before/after fields on the Frame AA and on the Image AA screens are no longer editable for PAGE-START and PAGE-END frames. Values are set/changed to 'N' for those frame types.
Bug #388: Cosmetic Query Process Level display bug
- The first two records of the Query Process scrolling image appear 'within' the box of the header frame.
- Fixed for 4.2.5.
Bug #776: Optional children can be added to Output/Inquiry processes
- Optional children could be added to Output/Inquiry processes via the Image Editor Toolbox option. By definition, optional children should only be allowed on interactive images in Menu/Input processes.
- Fixed for 4.2.5 - Optional children may no longer be added to any OUTPUT process images. Optional children may only be added to a KEY ENTRY frame of an INQUIRY process.
Bug #777: Empty Job Steps or Automatic Children
- When entering an empty job step to do certain tasks, you could not get into Rules, i.e., Option2). Rules does not work, when the App, Proc Type and Name are blank. Appx just ignores the option 2 request.
- Fixed for 4.2.5 - Options 0-99 may now be accessed in ADD mode as they could in 4.1.x.
- NB - Rules DOES NOT work as EL 0 when adding a job! (nor does Additional Attrribtues or Documentaion or Security, yet ALL of these buttons appear.)
Bug #825: Label GUI Attribute
- Fields defined as modifiable were not modifiable if they had a Label GUI Attribute
- Fixed for 4.2.5 - Items and their widgets are now checked to ensure that modifiable items only allow modifiable widget types to be defined. Edit checks were added to the item screens and to the widget screens.
Bug #922: Selection Expression button not highlighted
- The Selection Expression button for the end-user selection expression was not highlighted when an expression had been defined.
- Fixed for 4.2.5.
Bug #931: Option Number Off Display
- When selecting Event Point Rule if the Option Number selection was turned on and the list of event points was indented, the option numbers didn't display in the event point window.
- Fixed for 4.2.5 - Option numbers on Rules popups should now all be visible and aligned.
Bug #943: Use Query default name is stripped of leading spaces
- The defaulted Use Query (UQ) name stripped leading spaces from the query name
- Fixed for 4.2.5 - a Query name with a leading space will now be properly defaulted into the Query Name field of the Use Query spec with a leading space.
Bug #961: ILF and Image Changes do not flush EM/Dbg
- While designing a process, if you first use Option 99 to run the process, then use Option 97 to check syntax, from that point on, neither Option 97 or Option 99 will build a new Em even if you make changes to the process.
- Fixed for 4.2.5 - Note in Bug #819 that Option 97 (Syntax Check) always scratches the Em now.
Bug #964: Add'l Attributes on Optional Children do not work at Entry Level 0
- In 4.1.a, one could add an Optional Process and then press Add'l Attributes immediately. In 4.2, one must first save the OP, and then Add'l Attributes will work. Same holds true for 2) Rules, 4) Child Constraints etc
- Fixed for 4.2.5 - Options 0-99 may now be accessed in ADD mode as they could in 4.1.x.
Bug #1014: Auto Update
- Optional Processes are never suppose to run an Auto Update. Howver, the Designer is presented with Y/N Check Box in Optional Processes AND an error if the box is left empty.
- Fixed for 4.2.5 - removed all references to Auto-Update from the Optional Child Constraints screen.
Bug #1019: Application not modifiable in Query (SortOrder,UserSelection....)
- The Application was not modifiable in ADDMODE whan adding fields in SortOrder, UserSelction,DesignerSelection.... in a QUERY. Please note: This was only when adding the FIRST entry. In change mode the application was always modifiable.
- Fixed for 4.2.5.
Bug #1118: Process Management during Add Mode Entry Level 1
- The displayed options were not active during Add mode. For example, if you added a Job step, after typing in the Name, pressing option 2) Rules had no effect! Prior to 4.2, you could press the options during Add mode immediately.
- Fixed for 4.2.5 - Options 0-99 may now be accessed in ADD mode as they could in 4.1.x.
Bug #1121: AA indicator not lit when needed on Inquiry image
- The AA indicator is not always lit when it should be on an Inquiry image.
- Fixed for 4.2.5 - Synchronize Design Elements can be run to set attribute flags to their correct values for existing design records.
Bug #1126: Query Em doesn't get rebuilt
- Changing the 'Last' flag on the Sort Order screen did not trigger the Em to be rebuilt for the query.
- Fixed for 4.2.5 - Changing the last sort level flag now updates the mod fields in the Query Process and Frame records which will cause a new Em to be built.
Bug #1154: Relation field chopped off in Query Selection Entry
- When adding multiple designer record selection entries to a query, or when editing multiple entries that have been previously entered, the 'Relation' field was chopped to one character (instead of two) on records other than the top one on the display.
- Fixed for 4.2.5.
Bug #1158: Duplciate Alt-hotkeys in App Design
- The Optional Children screen had options for Child Constraints and Close that both use the C as the hot key.
- Fixed for 4.2.5 - The Close button will no longer have a Shortcut key defined. This change is global within Application Design. Close, Cancel, and OK buttons in Windows applications typically have no shortcut defined.
Bug #1199: Child specs need tighter edits
- Entry of an automatic child or optional child allowrf the Appl ID, Process Type, and Process name fields to be blank when they should not.
- Fixed for 4.2.5 - Appl ID, Process Type, and Process Name must now all be entered if any one or more are entered. Exception: Process name may be blank if Appl ID is specified and Process Type is Menu.
Bug #1208: Output frame level buttons do not display
- When designing an output process, if you used F4 to back up from the image level to the frame level, the buttons on the bottom of the frame screen did not display.
- Fixed for 4.2.5.
Bug #1211: Optional children could be added to a "display-only" input frame
- In input process design, Optional Children could be added to a 'Display Only' frame by using "hidden" option 4.
- The Optional Children button only appeared if the 'Display Only' flag on the frame was set to 'N'. However, if option 4 could be used regardless of the value of the 'Display Only' flag.
- APPX no longer allows optional children to be added to an image of a frame where 'Display Only?' is 'Y'.
- Optional chldren can now be added in ADD mode before editing the actual image provided that the 'Display Only?' flag is set to 'N'.
- The default value for the Display? field is now N, not Y.
Bug #1218: 'Display Only?' flag unexpectedly set to 'N'
- The 'Display Only' flag on an input process frame was sometimes unexpectedly set to 'N'. APPX allowed the designer to set this flag but then silently changed its value depending on other design specifications.
- This behavior caused confusion for APPX designers.
- Fixed for 4.2.5 as follows:
- The default value for the 'Display Only?' field is now 'N'.
- APPX never 'automatically' changes the value of this flag.
- APPX allows the designer to change the value of the flag to 'Y' only if no optional children have been defined on any image of the frame.
- APPX warns the designer if any modifiable fields have been defined on an image of a frame where 'Display Only?' is set to 'Y'.
- APPX warns the designer at the time that a modifiable field is being added to an image of a frame where 'Display Only?' is set to 'Y'.
- The default value for the 'Modifiable?' attribute of an Item is now 'N' when the item is being added to an image of a frame where 'Display Only?' is set to 'Y'.
Bug #1227: Cannot set Multiple Image flag in Output Image Editor
- After setting the Multiple Image flag to 'yes' on a record frame in the Output Process Editor, it was not preserved. This was true even if you set frame type to OPTIONAL in AA and also set the alternate image number in the Select Image event point. After adding one image at the image level, the frame level screen was presented and the Multiple Image flag was reset to 'no'.
- Fixed for 4.2.5b3 - This field is now system maintained and non-modifiable. The behavior of image maintenance has also changed slightly since you must now press END after adding an image in order to get back to the frame level.
Bug #1231: ILF Code can be lost
- In an update process, if you changed the Frame seq # to zero, then changed it back, you lost the ILF code in Start/End of process.
- Fixed for 4.2.5 - Frame sequence number may no longer be less than 1. This change has been made to all process types.
Bug #1262: Changing an output image number erases the Rules indicator
- If you change an image number for an output frame and the image has rules, the Rules indicator was no longer present. You have to access the Rules and return in order to restore the Rules indicator for the image.
- Fixed for 4.2.5.
Bug #1277: Cursor not positioned on image description when adding new output image
- When you add a new input image, the cursor is positioned on the image description. However, when you add a new output or inquiry image, the cursor is positioned on Extra Lines.
- Fixed for 4.2.5 - the cursor is now positioned on the image description field when adding an output image.
Bug #1289: Changes to INQUIRY process do not trigger Em rebuild
- Changes made via the image editor to an Inquiry process do not always trigger an Em build.
- Fixed by 4.2.5 0-apps
Bug #1302: Frame Size can be reduced despite presence of widgets on image
- It was possible to reduce the frame size on a record frame from, say, 10 rows to 6 without complaint, despite the presence of label widgets on rows 8-10. If you caught your mistake and put it back to 10, the widgets would reappear on the image. Note that you could not reduce it below 6 due to the presence of row text on the image for text output.
- Fixed for 4.2.5 - The size of a frame or image can no longer be reduced to a size that would result in an existing widget being anchored beyond the frame/image boundaries.
Bug #1333: Inquiry KEY ENTRY frame Rules does not highlight End of Process
- When End of Process rules exist for an inquiry process, 'End of Process' was not highlighted under Rules for a KEY ENTRY frame whereas it was for a RECORD frame. However, Start of Process, Post PCF Read, and File Level EPs were each highlighted when appropriate.
- Fixed under 4.2.5.
Bug #1360: Two buttons have the same shortcut
- The Additional Attributes button and the Automatic Children button on the Frame level of Output processes in Application Design both had A as the hotkey.
- Fixed for 4.2.5. The shortcut key for both automatic children and optional children is now 'C'. There is no shortcut key for the Cancel button or for the button that drills down to the next level of detail.
Bug #1394: OC attribute 'Auto Update' not modifiable
- For Optional Children the important attribute 'Auto Update' is not modifiable any more.
- Fixed for 4.2.5 - Reverted back to the orginal behavior for auto-update on optional children.
Bug #1408: Enduser Selection Button Mismatch
- In the display of Query Processes, the large button at the bottom was labeled 'User Selection', but the indicator button to the right of each processes had the label 'ES' as in 'Enduser Selection'. This was inconsistent and potentially confusing to designers.
- Fixed for 4.2.5 (Changed button to read 'Enduser Selection')
Design - Tech Doc (5 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Tech Doc
Bug #918: Unable to print Tech Doc for File Level Event Points
- Process documentation for a process type of File does not print the file level event points.
- Fixed in 4.2.5b2 - Tech Doc for file level event points can now be printed from Process documentation by selecting a process type of 'File'.
Bug #1120: Tech Doc prints two sets of Widget Attributes
- Technical documentation can print two identical sets of Widget Attributes for the same widgets, one before the widgets and one after. This was true for both PDF and text output, at least for Page-Start frames in Output and Inquiry processes.
- Fixed for 4.2.5.
Bug #1149: Tech Doc does not always print Transparent flag
- For example, Transparent didn't print at all for a numeric label widget (whether it was Y or N) but it always printed for an alpha TEXT AREA widget.
- Fixed for 4.2.5 - The default value for Transparent BG is 'N' for all widget types except for LABEL and PICTURE. The default value for LABEL and PICTURE is 'Y'. Tech Doc now prints the Transparent BG value only if it is other than the default.
Bug #1188: Occurrence number not printed for item widget in Tech Doc
- The occurrence number for a field name was not printed under either Widgets or Item Widget Attributes in Tech Doc.
- Fixed under 4.2.5.
Bug #1212: Tech Doc does not print Auto-Total Type or Extra Digits Left
- Technical documentation did not print Auto-Total Type or Extra Digits Left for output/inquiry processes. This was true of both text and PDF output.
- Fixed for 4.2.5 - Tech doc now prints the Auto-Total spec within the matrix. The digits left spec is now printed as part of the mask detail.
- The matrix headings were also changed to agree with the matrix headings that are displayed while designing. The only exception is the Mask column. When designing, this column is set to Y if either the Override DD spec is Y or if the Display Size (rows/cols) is non-zero. Tech doc prints both of these specs so it doesn't make sense to print a 'Mask' column.
Design - Transfer (4 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Transfer
Bug #711: Design Tranfer Output/Inquiry inconsistent
- Design Transfer - Output Processes and Design Transfer - Inquiry Processes are the only two Design Transfer processes that did not contain the phrase '(if different than From)' in the Transfer To box.
- Fixed for 4.2.5
Bug #753: Design Transfer - File Structure
- Most design transfers (Inputs, Outputs, and Queries for sure) allow multiple transfers, i.e., after transferring one, you can specify another. But with File Structures, after transferring one, it exits back to the main Tools Menu.
- Fixed for 4.2.5.
Bug #1013: Design Transfer - Anticipates Target Name too early
- When you design transfer, you can type in the beginning of the From object and press Scan. The new 4.2 improved Scan starts the search from that point and you can quickly select your From. However, the partial name you had typed in is automatically copied down below into the To Process Name!
- Fixed for 4.2.5.
Bug #1379: Design Transfer SCAN confusion crossing versions
Design - Utilities (4 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design - Utilities
Bug #1209: Xref blows up for files across applications
- The cross reference utility for "files" quit before completing if a file in another application was specified.
- Fixed for 4.2.5.
Bug #1213: XREF bug after editing referenced event point
- After editing an event point referenced by a cross reference, editing another event point before returning to the cross reference list resulted in unexpected cursor positioning within the event point. The cursor was not positioned at the beginning of the event point but rather at the line corresponding to the line referenced in the original event point.
- Fixed for 4.2.5 - When exiting from an event point, the 'navigate' fields are now cleared. If any other event points are subsequently accessed, the cursor will be positioned on the first statement as expected.
Bug #1294: Standard Output process generation tool needs tweaking
- Created a job/output selecting fields that had one-row column headings. APPX generated a Page-Start image with EMBEDDED BLANK LINES compression consisting of 3 rows. The 1st row was blank, the 2nd row had the column headings, and the 3rd row had '='s. At runtime, the report heading had problems under both PDF Output and text output. Using text output, there was no blank line between the report title and the column headings and there was an extraneous blank line after the '='s. PDF Output had an extraneous blank line between the column headings and the '='s and also suffered from Bug #1162 which corrupted the page heading.
- Fixed for 4.2.5 - The 'standard' report generator has been 'tweaked' as follows:
- 1) A Page-Start frame is no longer generated.
- 2) Standard column headings are now specifed for the generated output process as is a separator character of '='.
- 3) Column headings are no longer editable when specifying the fields to include.
- 4) Compress type on the output process, record frame, image is now set to 'NONE'.
Bug #1357: Sync Widgets utility updates Date/User Changed at process level
- Updating the audit info at the process level when running the Sync Widgets utility destroys very useful information for very little gain.
- Fixed for next 0-apps build in 4.2.5.
Design File Management (4 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Design File Management
Bug #578: Export an Application (Single File Export) - Target with No Directory
- When exporting an application, the resulting file was placed in a random directory if none is specified.
- Fixed in 0apps 4.2.5. We now default the pathname to $APPXPATH/{ver}/{ap}/PORTDSGN.txt, we check the pathname and give a warning if it does not include a path separator for the server platform, and we also now check that the portable stream file does open successfully before we start reading or writing data. This was missing before and it would cause memory corruption.
Bug #579: Export an Application (Single File Export) - Target with New Directory
- When exporting an App to a single file, specifying a New Directory, the export ran, but the directory was not created, no export file was produced, and no error was reported.
- Under 4.2.5, default export was to the same level as the Data and Struct directories and worked. Trying to export to a new, non-existent directory, Portdata failed, BUT does Error out: 'File Open Failed for portable file'.
Bug #580: Import an Application - Single File
- When entering Design File Management for a BRAND NEW App, there was no message of any kind, and since there is no PARAM file, you cannot Import an Application. Once files were created, import worked.
- Under 4.2.5, entering Design File Management now errors with 'Invalid Application/Version'.
Bug #909: 17) Convert From Pre 4.1 to 4.1
- In SysAdmin > DB/Appls > Design File Management, "17) Convert From Pre 4.1 to 4.1" should read, "17) Convert From Pre 4.1 to 4.2".
- Fixed for 4.2.5 - Changed to read, 'Convert From Pre 4.1'
DISAM (2 bugs)
Bugs Addressed in APPX 4.2.5 Relating to DISAM
Bug #835: 'This record already held by another user' unexpectedly encountered
- When returning to the parent process from the child process, APPX encountered the following errors: "ERROR - Record Not in File. This record already held by another user." When running with APPXIO instead of DISAM, these errors are not encountered. There were no other users or sessions running the same database.
- Fixed - Tested with 4.2.5.
Bug #863: REWRITE statement returns T but doesn't really rewrite
- REWRITE of PCF record in 'footer' frame of update process returns a T indicating success but the record is not really rewritten.
- Fixed for 4.2.3
Documentation - 0-Apps (4 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Documentation - 0-Apps
Bug #586: Item help on Named resouces does not match 4.2
Bug #887: Designer ILF Help
- ILF Help Screen did not include information on new options in the ILF Editor: 7) Select and 8) Paste.
- Fixed for 4.2.5 - The ILF Help screen has been updated.
Bug #893: Cache Priority Help Screen Correction
- On the help screen (F1) for the AA Cache Priority, the text said the default is 1. The default is actually 50.
- Fixed for 4.2.5.
Bug #1238: Input Default Key documentation is wrong
- The documentation for the Default Key field on an Input process was wrong. It states 'If blank, the primary key is used.' See bug #1210 for related info.
- Fixed for 4.2.5 - Field help text has been updated.
GUI - 0-Apps (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to GUI - 0-Apps
Bug #1374: Design Analysis - Check for Item Overlap
- If the number of rows defined is greater than 21, a bogus error was given for that process.
- This is not a problem with Item Overlap itself. The processes that seemed to generate incorrect results were due to corrupt data in the ITEM records for those items. The Item Size was set to 2 rows and 10 columns on an item that was a numeric 9(3) field. Set the item to --- TEMP 4 to get to the Item Size specs in the item AA screen to unset them, then set it back and it works fine now. The one that still errors out has items right up next to each other which Item Overlap still considers a problem. Another one has a ':' character typed on the image right after the field which Item Overlap considers a problem.
- Working properly in 4.2.5.
ILF Interactive Debugger (2 bugs)
Bugs Addressed in APPX 4.2.5 Relating to ILF Interactive Debugger
Bug #595: Non standard Row/Col sizes don't work
- Various non standard (ie, not 21 x 80) sizes didn't work right. If col setting was 120, then when running the DMO app the menu buttons are disabled. While stepping thru ILF code in debug mode, garbage characters may appear in the far right hand area where data values for fields are displayed.
- Fixed for 4.2.5.
Bug #1155: T/F Flags not visible when in trap mode
- When trapping through ILF code, the display no longer showed you the results of any conditional (IF, READ, etc.) statement. ALSO: The display while trapping no longer showed the process name or event point.
- Fixed in 4.2.5.
Install/Uninstall (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to Install/Uninstall
Bug #543: Can't print anything after installation or upgrade
- After a new installation on a new machine in a new directory, printing failed. The start of process executed, but never got to the Post PCF read.
- When upgrading an APPX installation on Unix/Linux via rpm, install.sh, makeself, or manually from tgz files, the permissions on the PRINT directory were typically recursively set to 755. This changed the permissions of the $APPXPATH/PRINT directory which apparently need to be 777 in order for printing to work successfully. The 'installers' need to explicitly set the $APPXPATH/PRINT directory to have permissions of 777 in order for printing to work after an upgrade.
- Fixed for 4.2.5. NOTE: If during installation you receive a warning that you are installing a 'secure' rpm and that you do not have the security key installed on your system, you can download and install the official APPX public GPG key with the following syntax:
- rpm --import ftp://ftp.appx.com/appx-rpm-gpg-key.txt
Java Client (27 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Java Client
Bug #58: PDF output to client printer always prints on default printer
- When you sent PDF output to a client (local) printer, the report was always printed on the default desktop printer even when a specific printer is identified in the Printer definition in System Admin.
- After upgrading the client JAR and Winprintdll.dll file to the latest version, this should be fixed so that when printing a PDF to a client printer, any printer name defined on the server will be used first. If this is not set, then the current value from the client Print Setup dialog will be used. If this has not been set by the user, then the client default printer will be used.
- For this to work, you must have a windows 'printto' command set up for PDF type documents. If you have Adobe acrobat or acrobat reader installed, this has already been configured for you. If you don't have a printo command configured for PDF documents, then the printer names will be ignored and if there is a 'print' command defined for PDF, printing will to go to the default printer.
- This all assumes Acrobat is installed. If not, then we just go to the client default printer.
- Fixed with client 4.2.5.b1 and client NativeWindows425.dll. Now when the print-to-client request includes a named client printer from the server PRINTER record, the client will grab the name of the current client selected printer, change to the new printer, submit the print request, then restore the prior printer name. So, the net effect is that the client printer remains unchanged from before the print request to after the printer request.
Bug #452: Java Client with large screens
Bug #551: Missing Graphical images - TMS, Main Menu with 32 rows
Bug #556: Changing screen Row/Col spec should not alter fundamental java display behavior
- Under 21x80, the header frame appeared to go completely gray. Under 30x132, the underlying java scrolling display degraded to almost win32 graphics.
- Fixed in 4.2.5.
Bug #600: File Chooser Limited to One Row
- GUI Attribute - File Chooser is still limited to one row. The bug is that the file chooser truncates the pathname even though the receiving field's internal length is long enough to hold the full pathname.
- Fixed in 4.2.5.
Bug #623: Java client freeze
- While quite extensively modifying gui attributes on an output process and then exiting outputs and entering Job Streams to print the output, the screen will freeze about once every couple of hours and the java session has to be killed and restarted.
- Fixed for 4.2.5
Bug #659: Java Client - Token Scan
- Typed IF --- OPTION EQ and pressed SCAN. Then typed A, and the list did not move down to the A's. Scrolling down with the vertical bar, ACK.. is highlighted blue, but the Token list did not move down as it would in earlier versions.
- See also #393, #659 and #791.
- Tested on 4.2.5.
Bug #677: Selected Record is not always 'selected'
- On a scrolling input, a click of the mouse on a record to be selected, usually selects the record immediately below the one selected, similar to having double clicked the mouse.
- Fixed in 4.2.5.
Bug #782: Java Client Hangs
- While entering Hook Records, specifying application --- instead of 0LA seemed to cause a hang.
- In repeated instances, when clicking multiple 'exit processes' to leave the (((great) grand) child)process, and then click an option to 'go back down' into constrained children, the client appeared to hang with an 'eternal hourglass'. Although this did not always happen, it seemed to be a common pattern when a hang does occur.
- Fixed for 4.2.5.
Bug #800: PREVious at a job step just does a pulldown
- When reviewing job steps, in CHANGE mode, the process type was highlighted. F4 to return to Previous Activity just caused a pulldown to occur on the process type. By tabbing to process name or backtabbing to appl ID, F4 performed as advertised to return to the job header. Or if in INQUIRE mode, F4 worked correctly.
- Fixed in 4.2.5.
Bug #805: Must Click Option Twice
- During input design, at optional children, clicking option 3 to select AA, only on the second click does the AA dialog arrive. Same for GA using option 6.
- Fixed in 4.2.5.
Bug #852: Duplicate Keyboard Shortcuts
- At various places in App Design, the Alt-P shortcut was duplicated, i.e., it activates the 'Process' pull down menu instead of what the user was expecting.
- Fixed in 4.2.5.
Bug #891: Focus remains on date chooser button
- After using the date chooser button to select a date, the cursor focus remained on the button on returning to the input image. If the user then pressed RETURN, the date chooser popup box re-appeared rather than the expected result (i.e. processing of the RETURN option by the image). Even if the user didn't press RETURN, the cursor focus was not obvious to the user.
- Another (related?) problem is that, after selecting a date with the date chooser popup and clicking OK, the date is not displayed in the field immediately. However, the date is displayed after tabbing to another field. This was not a problem in APPX 4.1.a.
- Fixed in 4.2.3 client. The focus should now shift back to the date field afer the date chooser is complete.
Bug #962: Box unexpectedly drawn around image
- Whenever a nonscrolling frame has set any GA on frame level, a border was auto created at runtime. Here the 2 possible 'box y/n' logical attributes on frame and image level are ignored - the border is also created if both are set to 'n'. As a result all buttons get auto disabled which are located in a display-only frame behind that nonscrolling frame.
- The process compiler currently forces the Box flag for a frame to 'Y' in the Em if a Frame or Image widget is defined. This causes a couple of problems: (1) A box can be unexpectedly drawn when running with a character mode client; (2) Buttons can be unexpectedly disabled in GUI mode because the client gets confused about which region should get the focus; (3) Widgets that are created or modified via ILF do not result in the same behavior since the flag is set at compile time and the widgets are created or modified after that point in time.
- Fixed for 4.2.5.
Bug #972: END from pull-down menu leaves empty white box
- Opened the (A)pplicaiton pull-down menu by pressing alt-A. Tried to close it by pressing ESC. The box where the pull-down menu appeared remained on the screen, though it was empty.
- This appears to work fine under java client 4.2.5.b1.
Bug #976: F1-F12 not working on text fields
Bug #1022: Pulldown menu bug: Keyboard options RETURN and ESC (resp. END) have no effect in pulldown menu
- If the pulldown menu is opened then a RETURN should activate the currently focused pulldown option. Also an ESC should close the pulldown menu.
- This appears to work as requested under java client 4.2.5.
Bug #1086: Java Client Image Editor text looks wrong
- The first time in a session in an output image that contains text and fields on the first row, the text is displayed in the wrong position. Going out and back into the image, it will display correctly, as will every image displayed after that.
- Seems to be fixed in 4.2.5.
Bug #1088: Java Client font changes
- After entering and exiting the Image Editor for outputs, the font that the Java Client is using has changed slightly (or something is not rendering it correctly).
- Fixed in 4.2.5.
Bug #1214: Cursor is not positioned where mouse is clicked in Image Editor
- In both the Input and Output Image Editor, if you used the mouse to click on a particular cell, the cursor was positioned one cell below and to the right of where you clicked on the image.
- Fixed in 4.2.5
Bug #1222: SCAN in ILF-editor hangs task
- Using scan to pick the literal value for a token field could cause the ILF editor to hang.
- Fixed for 4.2.5
Bug #1228: Backspace broken for ILF Editor Search
- When entering the search string in the ILF Editor using the Java Client, the backspace key does not work.
- Fixed in 4.2.5
Bug #1230: 28x80 Client Startup Breaks Wallpaper
- Starting the client with as size of 28x80 makes the APPX startup menu lose the background wallpaper.
- Fixed in 4.2.5 - Any client frame that touched the top, left, and right client window borders was merged into the main window. We no longer do this. An advanced client propert has been added called 'mergeBoxes' that can revert this change back if it is needed.
Bug #1270: Label value not displayed in image editor
- While editing an image for an output process, LABEL widgets are displayed as if they have no label value when the label value has one or more leading spaces.
- Fixed in 4.2.5.
Bug #1271: Pull-down list widget truncates table values if field is shortened
- The listbox item type operates with the non-GUI field entry both with respect to field validation and field value selection.
- This is fixed using 4.2.5 engine and 4.2.5b2 client for GUI mode clients. This is still a problem in character mode but has always been an issue in character mode.
Bug #1372: Can't Enter Data in Scrolling Input
- In a scrolling input child process, when the child is run, the user is unable to see what is entered. The cursor is not visible, and nothing visually changes when one types, but the data does in fact change, as error messages appear after pressing Enter.
- Fixed in 4.2.5.
Bug #1377: LoadUrl does not expand pathname tokens like SendFile and RecvFile
- Send and Recv File will expand spencial tokens like $(cachePath). LoadUrl does not.
- Fixed for 4.2.5.
Kit Build (3 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Kit Build
Bug #1175: Cosmetic issue - appx.exe version display
- If you right click on APPX.EXE, go to Properties and check the file version, you'd see under 'Comments' Appx 4.1.a Beta 2. This is really version 4.2.4.
- Fixed for 4.2.5.
Bug #1356: Wrong client version included
Bug #1383: Cosmetic? Full install shows 4.25b13 in Opt-99 vs
- Do the Opt-99 in the win32 client. The LHS says 4.25b13 for the engine release and the RHS stuff is all 4.25BE and the java client login and About say 4.25b14.
- Fixed for 4.2.5
ODBC Interface (Windows) (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to ODBC Interface (Windows)
Bug #1275: Asql doesn't find Database
- Sometimes, Asql doesn't find Database. If you put in Database ID and Application ID, nothing is returned. If Database ID is blank, but Application ID is filled in, you get list of databases. When you fill in just the Database ID, nothing is returned.
- Fixed for 4.2.5.
RDBMS Interfaces (2 bugs)
Bugs Addressed in APPX 4.2.5 Relating to RDBMS Interfaces
Bug #438: RDBMS restructure ignores Field (Name) overrides.
- The field overrides were all being ignored during a restructure (tested with Oracle 8).
- Fixed for 4.2.5.
Bug #1301: APPX ODBC fails to translate question mark to underscore
- APPX ODBC Interface on Windows failed to translate the invalid Access Field Name character '?' question mark to an ' ' underscore.
- Fixed for 4.2.5.
ReportWriter (SQL) (9 bugs)
Bugs Addressed in APPX 4.2.5 Relating to ReportWriter (SQL)
Bug #472: SQL - Report Writer - various issues
- Fixed for 4.2.5 - Release number will now match the release number of the 0-Apps. Release number on menu is now displayed from PARAM record for application SQL 00.
- Fixed for 4.2.5 - Tutorial screen has been enlarged by 1 row to allow room for all text.
- Fixed for 4.2.5 - Query Manager setup now allows DLU on all fields.
- Fixed for 4.2.5 - Query Manager setup now allows and provided HELP ITEM on all fields.
- Fixed for 4.2.5 - Copyrights have been updated.
- Fixed for 4.2.5 - Choose Application screen now scrolls a variable number of row depending on the screen size.
- Fixed for 4.2.5 - Choose Table screen now scrolls a variable number of rows depending on screen size.
- Fixed for 4.2.5 - The appearance of the choose table screen has been corrected.
Bug #477: SQL- Report Writer Item Overlap
- Report Writer was adding extra digits left and not adjusting the location when placing fields.
- Fixed for 4.2.5.
Bug #1047: SQL Report Writer requires c:tmp
- If you want the report writer to upload a delimited file, it will fail unless you have a c:tmp directory. Also, the file you create in c:tmp will be overriden without warning that it's going to do that.
- Fixed for 4.2.5 - The uploaded, export data file is now stored in $(dataCachePath). The name of the uploaded export file is now 'rptdata'.
Bug #1055: Exporting Data from SQL is mangled
- If the last column and first column on a report are both alpha, then the data was mangled when it was exported.
- Fixed for 4.2.5.
Bug #1106: Can't delete a query/report specification
- There is a button on the Special Functions Menu to Delete Queries. This doesn't seem to work.
- Fixed for 4.2.5.
Bug #1108: Tutorial pane missing - text incomplete
- The very first tutorial pane that pops up ends on an incomplete sentence. Should there be another pane after this one to continue the thought?
- Fixed for 4.2.5 - Tutorial pane now ends in a complete sentence.
Bug #1165: Sort Duplicated in SQL
Bug #1235: Export Options are not respected
Bug #1241: Can't set disposition for old queries
- In the pre 4.2 version of SQL, the user had an option on the menu to set the disposition options before running the query. In 4.2, that was replaced with a job step in the query that invoked --- INPUT DISPOSITION, like most APPX reports. The option on the menu was replaced with 'Export Options'. For new queries, this is not a problem. For queries created under 4.1 or earlier, the user no longer has a way to set disposition options.
- Fixed for 4.2.5 - When a saved query is retrieved, a Disposition step is added to the Job if the Job does not already have one. The query is also marked as having been changed. If the query is run, the disposition screen is displayed.
Runtime - 0-Apps (15 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Runtime - 0-Apps
Bug #671: Column headings clip report subheading
Bug #939: Auto Column Headings not right sometimes
- Auto Column Headings in PDF format sometimes got clobbered by multiple headings. Text format is much more graceful.
- Fixed for 4.2.5.
Bug #1031: Standard Page Headings wrong on PDF output
- If you print a PDF type report the date / time printed in the wrong spot. The Date/time, user and page number all printed on the right hand side of the report. In some cases, the date/time and page overprinted.
- The user ID, page number, and date-time are all on one side by design. The thinking was that users might like their logo in the upper left-hand corner. The fields should not overlap, however.
- Fixed for 4.2.5 - The standard page heading fields should no longer overlap.
Bug #1046: Query Date Mask ignored
- With a system date mask with no CC, and a date field CC-YY, with a date mask of 0807, the query presented the date field as YY only.
- Fixed for 4.2.5 or earlier.
Bug #1066: Scan doesn't return 1st record when is pressed
- When scanning a file, if the desired record is the first one on the screen, a simple return did NOT bring the record back. A mouse click on the record was required to get it.
- Fixed in 4.2.5.
Bug #1159: Option Help Missing on Default 'Operational Phase' Menus
- Appx supports multiple operational phases, and a Menu item can be added to a Menu with no process name, just Application ID and Type=Menu. Appx will then run the correct Menu based on the operational phase of the application/data. Unfortunately, the Optional Help is not as clever as the Menu processor - press Option Help, and you get 'Sorry, no help text available' when in fact the menu does have help text.
- Fixed for 4.2.5 - Now displays Option help for appropriate menu based on operational phase.
Bug #1160: --- GET ENV VAR limited to 22 characters
- The --- GET ENV VAR subroutine returns the value of a named environment variable. GET ENV VAR silently truncated the env. variable name to 22 characters.
- Fixed for 4.2.5 (Mote: the -- GET ENV VAR limits the name of the env. variable to 132 characters but the underlying RT GETENV callable function is no longer limited.)
Bug #1192: Standard Subtotals not graphical for PDF output
Bug #1194: Appx Hangs When Canceling from Scan
- When END or CANCEL are entered while a scan list created by NSCAN JAVA is open, the Appx session hangs due to an overflow error and has to be killed.
- Fixed in 4.2.5.
Bug #1195: Non-integer query field re-displays blank for zero
- A blank field is being displayed on a query record selection non-integer field when the value entered is 0. This occurs when record selection screen is re-displayed (F4) from the sort select screen.
- Fixed for 4.2.5 - numeric constants that are entered in query selections should now be redisplayed when using Previous Activity even when the entered value is 0.
Bug #1220: TEMP 80 contains garbage after scan
Bug #1246: Hangs trying to open SOP EP
- Logged on to APPX, into Design, selected TPA 04, Updates, EMPL EARN STATEMENT U, Start of Process, hang. < 5 minutes total. Hangs in CHG mode too. Hangs trying to access the Record SOF EP also. It appears that you can't access ILF at all. Hangs trying to access Select Image in an Input process also.
- This is fixed in 4.2.5.
Bug #1257: Select Path button missing in Scan
- When you do an F2 scan, there is no 'Select Path' button. Option 2 still brings up the Select Path window.
- Fixed with 4.2.5.
Bug #1293: Sending e-mail from Print on Screen doesn't include report
- On some platforms, sending a report as an e-mail from Print on Screen results in an empty e-mail or an e-mail that contains the comments but no report.
- Fixed with 4.2.5 0-apps.
Bug #1404: Improper tooltip for Execute button on Select a Database
- If you selected 'Run an Application' from the APPX system menu, the tooltip for the Execute button on the Select a Database popup read 'Execute the Change All References'.
- Fixed for 4.2.5. Changed to read 'Run the startup application for the specified database'.
Runtime - APPX Engine (41 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Runtime - APPX Engine
Bug #466: Too Many Error Messages
- If for a specific record in an output process, more than 50 ERROR, WARNING or MESSAGE commands were generated, the APPX output weny into an infinite loop. Ultimately the APPX session had to be killed, otherwise the print directory ran out of space which may cause the system to crash.
- This was reported sometime ago and is in the ECR system as #5684. A workaround has been defined to replace ERROR statements with WRITEs to a memory file. This was being done for anything new generated.
- Fixed for 4.2.5
Bug #480: AT FIELD always 'F' in INQ if field Entry Level > 1
- In an INPUT process, in Inquire Mode, if a field had an entry lever of >1, then the AT FIELD in Option intercept with that field as operand, always returned F.
- Fixed in 4.2.5.
Bug #660: GUI Title Bar disappears
- An INPUT process' Frame-Size-Rows of less than the default of 21, caused the GUI (Window Properties) TItlebar-Options 'Title' attribute to not display a titlebar at runtime.
- Fixed in 4.2.5.
Bug #681: 'Option' spec ignored on Child Widgets
- Option can now be specified on a child widget. This option is supposed to override the implied option of USER nnn for an optional child. However, APPX was ignoring the option when it is specified. The standard toolbar process takes advantage of this feature. As a result, toolbar buttons are firing the wrong options.
- Fixed in 4.2.5.
Bug #819: Automatic Recompile is NOT Happening Automatically
- In order to get a good recompile of multiple depths of GOSUB's, it was necessary to delete EM's for all apps involved, then recompile recursively, starting at the bottom and working to the top, sometimes having to change code to get Option 97 to actually perform the Syntax Check.
- Fixed for 4.2.5 - Option 97 (Syntax Check) now scratches the Em thereby forcing APPX to always compile the process
Bug #841: Passing Groups with Token field element fails to pass
- Pass of a group header with a Token element did not work. Received the same group header, but the third part of the field was not there. When passing and receiving the three fields separately, it worked fine.
- Fixed in 4.2.5.
Bug #850: Invalid Date(s)
- Using DATE ADD to subract one day from 21010101 caused a runtime error, Invalid Date.
- Fixed for 4.2.5.
Bug #851: 30 column scan fails
- When scanning on a field that uses NSCAN (30) the user received an Appx ILF error on a DEFINE statement for --- ENTRY KEY FLD VAL ZI. All other scan screen sizes seemed to work fine.
- Fixed for 4.2.5.
Bug #875: CNV TEXT corrupts memory when receving field too small
- Used CNV TEXT to set SSY WORK ALPHA 12 = --- OPTION. --- OPTION is 22 characters, receiving work field was smaller. Resulting error: "mm free() - corrupted trailer (AREA: DOC:2.7)".
- Fixed in 4.2.5.
Bug #879: Display item sequence out of whack on generated subheading
- APPX used to string the display items on a generated subheading in DD field sequence number order if all the items had Display #1. It doesn't seem to do that anymore; in fact, the display order is somewhat unpredictable.
- Fixed for 4.2.5. - note: fields with equal Display Sequence numbers will print (left-to-right) in offset order, not sequence number order. That only makes a difference for synonyms and substrings.
Bug #906: Mod logs don't display occurrences correctly
- If the PCF for a process contains any multi-occurrence fields, the modification log entries for a CHANGE operation were incorrect. The mod log seemed to skip every other occurrence, and the values shown were associated with the wrong occurrence numbers.
- Fixed for 4.2.3.
Bug #907: Mod logs show deleted record values in wrong column
- The modification log entries generated for a DELETE showed the PCF values in the 'New' column instead of in the 'Old' column. This conflicts with the way Speed II mod logs were produced.
- Fixed for 4.2.3.
Bug #910: Printing of PDF files with Windows doesn't honor specified printer
- APPX/Windows executed a 'Print' action to print a PDF file. The prior implementation did not honor the specified printer and instead always sent output to the default printer.
- Fixed for 4.2.5.
Bug #911: Printing of PDF files with APPX/Windows doesn't honor APPX PRT SCRIPT
- APPX/Windows did not honor the APPX PRT SCRIPT environment variable when printing PDF files. This prevented PDF output from being queued to print spoolers.
- Fixed for 4.2.5.
Bug #925: End of Process (Query Setup) EP does not always run
- If a query was executed without first having executed a QUERY step in the job, the End of Process (Query Setup) EP did not run. The Start of Process (Query Setup) EP did run.
- Fixed for 4.2.3
Bug #927: Trailing sign not honored for integer numeric field in output
- APPX assumes a trailing sign for a numeric field with decimal places if no display mask is specified on an output image. However, if the numeric field is defined as an integer in the DD, the space for the trailing sign was not preserved at runtime; a positive value is shifted to the right, thus causing misalignment. This is true even if an explicit display mask (90-) is used.
- Fixed for 4.2.5. But the trailing sign position is only honored for a widget field on PDF Output. See Bug #1367 to address the remaining problem with text output and with non-widgets on PDF Output.
Bug #935: Date Chooser Returns Blank Date
- Clicking on the Date Chooser Icon returned a blank date.
- Fixed for the 4.2.3 release of the Java Client.
Bug #953: Runtime C-assert caused by exceeding maximum size in Output Image Editor
- An APPX system error 'image rows exceeds maximum size' appeated at runtime using an output frame with 24 rows of 95 columns. When reduced to 21 rows of 95 columns, it worked fine.
- Fixed for 4.2.5 - increased the maximum (output) image save from 21 rows to 255 rows.
Bug #963: Can't select by keyboard on single-field-display file scans
- When scanning on a data lookup into a file for which only one field is defined as displayable, selecting with the mouse brought back the desired record, but trying to select by using cursor arrow keys and ENTER brought back no result at all.
- Fixed for 4.2.3.
Bug #1026: Scan fails with seg fault
- Invoking scan from within a live application caused a seg fault.
- This appears to be fixed under 4.2.5.
Bug #1045: Automatic subtotal not properly aligned in PDF output
- If a column is eligible for totaling, the automatic subtotal image provides for a total amount with a single line above and a double line below (='s). On PDF output, each of these items were right-aligned with the trailing sign position of the column, rather than the right-most digit position. On text output, the total amount was correctly aligned but the single and double line of dashes was one to the right, the same as PDF.
- Fixed for 4.2.5.
Bug #1076: Record locking/error message issue
- Two designers got the same idea at the same time -- to change a flag on TGL PARAM. It's not normally editable, though, so one temporarily added it to the regular F/M process while the other used the Generate utility to create a new input for it. Then both simultaneously tried to change it. But they didn't get a 'record held by another user' message at all. Instead it reported that TGL PARAM was NOF. One user thought maybe it needed restructuring, so tried that, which hung for awhile (the other must've had the record held). It would seem that one should have received a 'record held by another user' error message. (Further details on this problem are documented in the APPX Bug Tracker records.)
- Fixed in 4.2.5 as follows:
- Improved the error message text so that a 'file in use' error will now display as 'File Opened For Exclusive Use By Another Session' instead of the old and confusing 'Access Mode Reserved By Another User Or Stream'
- Improved the layout of the CANCEL screen you see if an I/O statement fails with a FT of 3 (you'll now see the same screen that you would see had you executed a CANCEL statement).
- Fixed bug #619 so you can now enter (and edit) a READ statement on a one-record file (and leave the key-field blank).
- Fixed the SCAN display in the ILF editor so you see nicely explained choices if you scan on the FT (or HOLD) field(s).
- Fixed the ADD mode problem - you'll now see a nicely formatted message that tells you the file is opened for exclusive use by another session.
Bug #1077: STANDARD MOD LOG
- There was a CNV TEXT 'bug' in the 0LA Output STANDARD MOD LOG. The bug is that CNV TEXT did not blank out the receiving field, but only added new text.
- Fixed for 4.2.5. CNV TEXT now appears to 'blank' the target before converting the text.
Bug #1123: Scrolling Input missing record
Bug #1141: Windows Properties WIDGET not working when rows > Image (Menu)
- For a Menu process, setting a background color is not honored when running with extra rows.
- Fixed in 4.2.5.
Bug #1161: Invalid Window Size reported for centered windows
- If you tried to run a process whose frame (or image) is supposed to be centered, you'd get an error 'Invalid Window Size' if the size of the frame (or image) was larger than the size of the client window.
- Fixed for 4.2.5 - Bug #848, which is marked as a duplicate of this one, has been fixed.
Bug #1179: Process Compiler Hangs
- In an output process that has a frame with zero lines and no compression, the Process Complier would hang.
- Fixed for 4.2.5.
Bug #1182: Change mode while in key entry
- If you CHANGE MODE twice, while in key entry, it brought up the last record you were on, instead of going back to the first, on non-scrolling input frames only. If you changed input to the scrolling frame, the problem went away.
- Fixed for 4.2.5. FYI - You can get back to the old mode switching logic by creating an env. variable named APPX OLD MODES.
Bug #1183: DLU from Record Selection Ignores DD Display Sequence
- When using SCAN to select a key value in Record Selection, the display of fields was presented in field sequence order, ignoring the display sequence value.
- Fixed for 4.2.5.
Bug #1189: Internal error encountered upon return from PDF tech doc
- After printing tech doc in PDF format to the screen, an 'Error - An internal error has been detected, proceed with caution!' was issued when returning to the Documentation menu.
- This seems to be fixed under APPX 4.2.5.
Bug #1202: SCAN unexpectedly modifies the values of the source fields
- When SCAN statements are used to define a SCAN, the source fields are in the file that is being scanned. The destination fields are the fields that are to receive the values from the source fields of the record selected from the file being scanned.
- When scanning a file in APPX 4.2.x, the values of the source fields were unexpectedly being modified. This was not the behavior of APPX 4.1.x. Consequently, invoking a scan could unexpectely modify field values that were not modified by a scan in previous versions of APPX.
- Depending on the circumstances, this could break existing applications. For example, it was no longer possible to scan when defining a DLU on a field without corrupting the FIELD record. (see bug report #1095)
- Fixed for 4.2.5.
Bug #1206: Row position of item in Inquiry process can disrupt printing
Bug #1221: AT FIELD has no effect in Global Option Intercept event point
- The AT FIELD statement did not return the correct T/F if used in the Global Option Intercept event point. It always returned F.
- Fixed for 4.2.5 - The AT FIELD statement now works as documented when used within the Global Option Intercept event point.
Bug #1237: Random system errors encountered running Tech Doc
- Ran TECH DOC to the screen twice, first as text output and then as PDF output. When returning from viewing the PDF version in Adobe, encountered an 'attempting to free unallocated memory' system error. Logged off APPX and logged back on to see if the error could be reproduced. This time, when attempting to print the same tech doc using text output, an 'elem is null' system error appeared before it printed anything to the screen.
- Fixed for 4.2.5.
Bug #1274: Usage log can overwrite system admin files
- The problem is that you can specify any file name, including an exising 0SA file and APPX will overwrite it. Tested with SQL.dat, and it overwrote SQL.dat with log file data (did not have the courage to try a more important 0SA file).
- Fixed for 4.2.5 - If your log file attempts to overwrite a 'reserved' file, you are now informed of this at runtime. APPX also assigns the logfile a different filename and advises you of this new filename.
Bug #1281: Problems with query-constrained input processes
- When you try to NEXT-RECORD past the end-of-file in an input process that has been constrained by a query, you get the error 'Position Undefined'.
- Fixed for 4.2.5.
Bug #1306: Can't SCRATCH file via APPX/Net
- If you try to SCRATCH a file on a remote server, APPX just returned to the calling process without giving any indication of a problem. The file was not scratched.
- Fixed for 4.2.5. The SCRATCH correctly returns a F instead of just ending the process.
Bug #1338: Can't hook 0LA STANDARD TOOLBARS
Bug #1339: TAP Checks Approval behaving badly
- The Checks Approval process in TAP consists of an Input process (CHECKS APPROVAL AND REVISION), its automatic child (CHECKS APPROVAL AND REVISION 2) and an optional child (SEQUENCING OPTIONS) that can present one of several screens depending on whether you're approving or revising (reprinting, voiding, etc) a series of checks. SEQUENCING OPTIONS has three frames. The first one displays info regarding the batch of checks. The second one displays one of several images depending on what you're doing with the checks. The third one optionally displays to allow you to begin assigning check stock numbers. These processes have always worked fine in the past. Now, after entering the transaction numbers I want to approve, I press Return, the screen paints the third frame image but then greys out the OK button and I can't highlight the stock number field, so I can't enter the beginning check stock number. Which means I can't approve the checks. Or print the Journal or Check Register. Much less post the checks.
- Additional info: A similar situation exists in Hand Checks Entry 2 in TAP, if you're entering a hand check for a Miscellaneous Vendor. This scenario still works fine. The major difference is that the OK button in the second scenario is painted on the first image, whereas the OK button is painted on the second image in the original (malfunctioning) scenario. To test the second scenario, run Hand Checks Entry, select the first control group, then go to the third transaction.
- Fixed with 4.2.5.
Bug #1373: Can't create UNC-based directories
- If you try to create a file with a UNC-based pathname, the attempt will fail with a File Not Open error (UNC-based pathnames start with \hostshare).
- Fixed for 4.2.5.
Bug #1389: Next Record after end of file in Inquiry causes Position Undefined error
- If you do a Next Record after the system has reported 'No More Records' and the key field is blank, you will get an 'Error - Position Undefined' message. On the other hand, if you simply press return, the inquiry will bring up the first record in the file.
- Fixed under 4.2.5. Changed it to the less accurate but more obvious No More Records.
Runtime - PDF Output (91 bugs)
Bugs Addressed in APPX 4.2.5 Relating to Runtime - PDF Output
Bug #85: PDF Output - Invisible doesn't work
- The 'Invisible' check box is editable on the GUI attributes screen in Output processes. But it did not make the field invisible if checked.
- Fixed for 4.2.5 (note - we haven't fixed the compress-blank-lines part of this bug yet, that's a separate issue).
- Currently, on PDF Output, if the widget Invisible flag is set, nothing prints. The item Invisible flag is ignored for both PDF and text output. On text output, the data always prints (logged separately as Bug #1320).
- There is a hierarchy that applies in the case where the item and the widget have redundant attributes that are inconsistent.
- 1) The widget attribute applies unless it is null.
- 2) If the widget attribute is null or if there is no widget record, then the item attribute applies.
- 3) If the widget attribute and the item attribute are both null, then the APPX engine has the responsibility for deciding how to interpret the attribute. In the case of the 'Invisible' attribute, the engine will treat a null value the same as 'N'. In other words, the field will print.
Bug #159: LABEL/PDF - ETCHED border not etched on hard copy
- Neither the ETCHED SUNKEN or ETCHED RAISED borders for a LABEL widget appeared etched on PDF hard copy. Using the default border color, the border for both looked like a grey SIMPLE LINE border.
- PDF Output printed fine under 4.2.5.
Bug #192: Frame/Image Widget Properties Border not based on Frame dimensions
- The border defined in Window Properties was drawn based on the rows and columns defined for the report overall, not on the rows and columns defined for a given frame. The border should be drawn around the frame coordinates.
- The widget is actually an image level widget so the border should be based on the image size. This would be especially true if there are alternate images of varying sizes. We do not currently have a widget that defines graphical properties for the frame. If you specify widget properties at the frame level, those are used as default properties for the images.
- Fixed in 4.2.5.
Bug #193: Icons not printing for Window Properties
Bug #215: Box borders are barely visible
- Etched borders, and two sides of each type of bevel border, were barely visible when printed on a BOX widget.
- Fixed for 4.2.5 (increased border widths and darkened default border color).
Bug #224: BOX widget doesn't honor Invisible? parameter on PDF output
Bug #263: Float Spaces loses or distorts data on PDF Output
- If an alpha LABEL widget is defined to float spaces, the data field contents were lost or distorted on PDF Output.
- Fixed under 4.2.5.
Bug #273: PDF: Text item TEXT AREA widget not compressed
- Compression types EMBEDDED, TRAILING, and EMBEDDED/TRAILING did not properly compress blank lines in a text item TEXT AREA widget.
- Fixed under 4.2.5.
Bug #279: Box fill color overruns box boundary
- When you assigned a fill color for a box, it looked fine on the Image Editor, but when printed it overran the boundary that contained the title.
- Fixed in 4.2.5.
Bug #298: PDF Output loses widgets if image has New Page Before
- Setting New Page Before = Y at the Image level of a Range-Start frame caused the widgets to be stripped from the image before printing. This was not true if New Page Before is set at the Frame level (On the very first page it printed correctly, probably because it's not actually skipping to the next page). Also true of RANGE-END and RECORD frames.
- Fixed in 4.2.5.
Bug #316: LABEL/PDF ETCHED borders w/color different from output image
- Label widgets with ETCHED SUNKEN or ETCHED RAISED borders with border color appeared differently on PDF Output than on the output image. In particular, all four sides of the border are treated the same on the output image whereas two sides are bolder than the other two sides on PDF Output.
- Fixed under 4.2.5.
Bug #324: PDF Picture scale doesn't print correctly
- Using the Image Scale parameter on a PICTURE widget looks OK in the Image Editor but didn't print correctly.
- Fixed in 4.2.5.
Bug #360: Data LABEL/PDF: Right margin is not honored on PDF Output
- The right margin for an alpha label widget was not honored on PDF Output whereas left/top/bottom margins all appear to work fine.
- Fixed for 4.2.5
- Fixed also under APPX 4.2.4 with patch for this bug.
Bug #361: Data LABEL/PDF: Height/Width micro adjustments not honored on PDF Outpt
- Height and width micro adjustments for an alpha label widget did not work on PDF Output whereas row and column micro adjustments appeared to work fine.
- Fixed under APPX 4.2.5.
Bug #366: PDF Output - extra lines added to last frame on page
- One extra line was being added to the last frame on a page if there were borders, 3 lines if no borders.
- Fixed with 4.2.5.
Bug #369: Data PICTURE/PDF: Icons do not print for alpha picture widgets
- The contents of the alpha field were printing, not the icon, for an alpha picture widget. This was true for both location type Design File and Client File.
- The original complaint of this bug has been fixed. The other problems that cropped up along the way are submitted as separate bugs. See Bug #1288 (picture widget with shrink Null not printing), Bug #1290 (PDF Output hanging if Picture alpha item is blank), and Bug #1291(Picture alpha items with shrink Null not printing if compressed).
Bug #446: Resolution of some PDF label textual problems
- Text within a label widget was being truncated unless at least one extra cell was available left and right of text within a label widget.
- Fixed for 4.2.5.
Bug #479: Garbage prints for multi appearance fields
- A work field is placed several times on the image. Auto Display is off, and display is controlled by ILF command referencing the appearance number. The field is calculated, but if an overflow occurs, the code branches to a location that sets the field to zero. The field is always DISPLAYed at each appearance number. AA for the field has 'Blank if zero' checked. The appearances that contain zero print as garbage.
- Fixed for 4.2.5.
Bug #481: Trailing Blank Lines Compression doesn't work
- In an output frame 21 x 128 that contains a text field 18 x 119, with compress type on the image set to 'Trailing Blank Lines', trailing blanks were not compressed out, and the next image started at the end of the defined image.
- Fixed for 4.2.5.
Bug #482: Justification of multi line label doesn't work
- With a work field on an image, as a LABEL control type, specified Times Roman, Bold, 175%, 2 rows in size. Trying right and center justification, but neither would align properly. When resized down to one row, justification worked as expected.
- Fixed in 4.2.5.
Bug #500: LABEL/PDF: Change PDF Output to match Image Editor
- This bug is prompted by Bug #313. It involves differences in text/icon positioning between what you see in the Image Editor and what you get on PDF Output. Since the Swing library dictates what can be done in the Image Editor, PDF Output should be changed in order to achieve WYSIWYG.
- The most glaring differences involve icon positions ABOVE & TRAILING, ABOVE & LEADING, BELOW & TRAILING, and BELOW & LEADING. To the untrained eye, one might think that these would be treated similar to ABOVE TEXT and BELOW TEXT and just adjusted for trailing or leading, as they are in PDF Output. However, the Swing library apparently has different rules (see comments in Bug #313).
- Fixed for 4.2.5.
Bug #504: Boxes with micro height adjustment are not WYSIWYG
- Two empty boxes drawn on a form. The height is set to 50, and it looks fine in the image editor, however, when printed to PDF, there is a vertical line that connects the two.
- The vertical line was caused by the boxes overlapping.
- Seems ok in 4.2.5.
Bug #506: Text wraps funny, adds extra blank line
- With a large description field on an image, control type TEXT AREA, font Arial, Scale 140, the first part of a sentence printed fine. The line following is empty and the line below that has the last part of the sentence.
- Fixed for 4.2.5.
Bug #614: Image 'Characteristics' don't print
- Row text that has the Underline or Bold characteristic set did not print with the specified characteristics when the report is printed as a PDF document.
- Fixed for 4.2.5.
Bug #625: Invisible attribute on label not working on PDF output
- Trying to make some labels on a PDF output invisible in certain situations was not working. Tried with ILF code and by actually checking the box but the label still appears on the output. The invisible attribute works fine in Inputs.
- Fixed for 4.2.5.
Bug #668: Missing label widget in Page-Start frame
- The first label widget defined in the column headings did not print on PDF Output nor does it appear on the output image (similar to Bugs #637 and #649).
- It seems this problem was caused by the specific position of the label widget on the line, not by whether it is the first or last widget. A widget starting in position 1 on the first line did not print; if it started in position 2, it did. It also printed OK if you micro-adjust it back to position 1.
- Further research showed similar behavior at other positions in the first line of output.
- Fixed for 4.2.5.
Bug #672: PDF Output prints designer column headings under page head
- Mostly, column headings work fine with the exception of the line number problem on the separator line. But, in one case, it is printing the designer-defined column headings on line 2, under the page heading (all you can see is the 't' of 'Unit' in the last column of line 2). This bug is somehow related to the frames of this output process starting in position 4 instead of postition 1. Changing them to print in position 1 causes the report to print correctly.
- This particular bug appears to be fixed under 4.2.5. However, in the report cited, the separator character is now being ignored. See new bug #1205.
Bug #785: PDF Output - Compression
- With multiple labels on an image, even if the label is blank, there is no compression. An example of this can be found in TAR 04, Output TRANSACTION REGISTER REPORT, in the Column Headings (Page Start). There is an optional title that should be compressed if blank, and it is not being compressed.
- Fixed for 4.2.5.
Bug #853: Page-Start frame starting in Position >1 overwrites page heading
- If a position other than 1 was specified on a Page-Start frame, it overwrote the company name line in the standard page heading.
- This particular bug seems to be fixed under 4.2.5. However, there is now another bug involving page separators, see bug #1205.
Bug #860: Trailing Blank Line not compressed on Page-Start image
- If a data widget was defined on the line, a blank line would not be compressed. This is true regardless of whether the data is blank or if a BLANK statement is used. The data widget in this case was a Label widget on an ordinary alpha item, unlike Bugs #273 and 481 which deal with compression not working on text item Text Area widgets. This problem also occurred on a Range-Start image. However, compression works properly on a Record image.
- Fixed under 4.2.5.
Bug #900: Auto-Display question marks duplicated on Range-Start image
Bug #965: PDF Output dropping widgets
- Creating special forms for PDF Output. A LHS 'Date Required' Label is missing, and a RHS 'Terms' Label is missing. It's also dropping widgets from the final footer window on the Invoice.
- These might be some blind spots like those recorded in Bug #668.
- Fixed for 4.2.5.
Bug #967: PDF Output not honoring Characteristics
- Assigned a Characteristic of Blue to the dashed lines separating headings from their respective totals. APPX is printing black.
- Fixed for 4.2.5.
Bug #980: PDF Output - Data Size Mask
- In PDF Output, trying to get fields to compress horizontally, neither "float spaces" nor specifying a display mask smaller than the field definition worked.
- Fixed in 4.2.5.
Bug #995: Lines After on frame, not image, can cause blank page
- In PDF output, if "1 Line After" is specified on the record frame at a lower level, it can cause an extra leading blank line before the line items on page 2 or higher. In turn, the last line of the footer can be lost and a blank page can occur at some point. Meanwhile, it works fine if PDF output is not called for.
- This bug appears to be fixed under 4.2.5.
Bug #1065: PDF Output doesn't work with codepage 950
- If the server is using codepage 950 (Traditional Chinese Big 5), then APPX generates a C-Assert when PDF output is attempted. This happens regardless of whether the data contains multi byte characters or not.
- May be fixed for 4.2.5 - on Windows hosts, character encoding is now inherited from the server. You can also define an environment variable named 'APPX PDF ENCODING' to override the server settings (set that env. to a string like cp950).
Bug #1098: PDF Output not honoring right justification
- Defined a subtotal label widget as right justified, and all of a sudden APPX is treating them as centered instead. (Related to Bug #482.)
- Fixed for 4.2.5.
Bug #1119: PDF Output won't compress widgets
- When using TRAILING BLANK LINES compression, APPX didn't recognize that a field is blank if it's a widget.
- This type of problem appears fixed under 4.2.5. See Bug #273.
Bug #1135: PDF Output putting garbage in work fields
- Using a right-justified work field, instead of a left-justified work field with the widget set to right justify, APPX loaded the RJ work field with garbage. Also, if you paint a right-justified work field on an input process (make it more than one row high), you got garbage. Same result on a text-mode output process. It's apparently the justification logic that was broken.
- Fixed for 4.2.5.
Bug #1147: PDF Output not representing margins correctly
- PDF Output was no longer representing margins correctly, at least not right margins.
- Fixed for 4.2.5.
Bug #1151: Field under picture blows widgets away
- Placed a 2-line text field (Logo Address) directly under a Picture widget, and none of the widgets in that image printed. Moved the address field down a line, and they printed.
- The 4.2.5 fixes to Bugs #613, #954, and #959 appear to have fixed this bug also.
Bug #1162: PDF Output corrupts page heading if Page-Start has compression and widgets
- If a Page-Start image had compress type EMBEDDED or EMBEDDED/TRAILING and widgets were also defined, the report title could be lost. In addition, the date or user ID might overlay the page number and the spacing of text on the image might be distorted.
- Fixed for 4.2.5. PDF Output no longer corrupts the page heading if a Page-Start frame has compression, widgets or no widgets. However, the Page-Start image itself may be distorted which has been logged as a separate bug (Bug #1317).
Bug #1163: PDF Output Print Beside behavior has deteriorated
- Print Beside works properly in text mode but has problems in PDF Output. Start Print Beside is set on the Range-Start frame. PDF Output now prints the auto-generated subtotals beside the Range-Start frame, overlaying the detail that has already printed beside the subheading. If Start Print Beside is also specified on the Record frame, it overlays the last detail line instead of the first.
- Fixed in APPX 4.2.5 w/Print Beside fix.
Bug #1181: Right Justification truncates text
- Using a field which is X(7) right justified. Filling it with either a 6 or 7 character value. The field is painted as a label widget on the report at 125% scale, stretched to 2 rows and 9 characters to allow for the expansion. When the report prints you lose the last five characters of either value.
- Fixed for 4.2.5. (If left blank, the widget text position inherits from the underlying field (for item-related widgets)).
Bug #1184: Standard Grand Total generating page headings
- An output process has two frames, a Page-Start frame and a Record frame. The Query is basically vanilla, with some End-User selections and a Sort Order, with Grand Totals listed as Standard and editable. But when you print the report, the Grand Totals would appear with the Page -Start frame overlapping it.
- This bug was fixed in 4.2.5.
Bug #1193: Standard page headings are broken for PDF Output
- Standard page headings were missing or corrupted when printing to PDF output for many reports. It only appearred to happen if the report contained widgets in one of its frames (not necessarily a Page-Start frame).
- Fixed in 4.2.5.
Bug #1205: Page Headings are sometimes missing the separator line
- The separator line for a standard page heading sometimes did not print for PDF output.
- Fixed for 4.2.5.
Bug #1215: Some row text may be missing on PDF Output
Bug #1239: Text item w. Text Area control does not fill col spec
- If you define a text field on the image as 15 rows x 23 col but specify a scale factor of 75% in the TEXT AREA widget control, you did get the 75% scaling but APPX does not print up to the 29 characters which should fit in this 23 col space at that scaling.
- Fixed for 4.2.5.
Bug #1252: PDF Output not honoring micro adjustments on boxes
- Boxes painted as vertical lines on an output image are printing as boxes instead of a vertical line because the micro adjustments are not being honored.
- Fixed for 4.2.5
Bug #1253: PDF not printing correctly when blank lines are compressed
- Output processes print with a variety of strange problems when blank line compression is specified and PDF output is requested.
- Fixed for 4.2.5
Bug #1254: New engine shrinking widgets too far
- Test release is shrinking some widgets too far and clipping text off. Note that the report heading is OK in the 16-pitch report, but the subheadings are getting clipped, whereas in the 10-pitch report it's the page heading that's getting clipped.
- Fixed in 4.2.5.
Bug #1255: Print Beside broken again
- Outputs with "print beside" are broken again. This time it is printing on top of the leftmost column. Text version works fine.
- Fixed for 4.2.5.
Bug #1258: Not all trailing blank lines are being compressed
- Output images with compress 'Trailing Blank Lines' sometimes still have one or more blank lines.
- Fixed for 4.2.5.
Bug #1259: Token field print garbage
- Token field printed 'garbage' instead of the correct value. It appears that the one byte binary value was being printed. This does not seem to apply to tokens that have not been widgitized.
- Fixed for 4.2.5.
Bug #1260: Output Widgets do not honor transparency spec
- All output widgets seem to have transparancy regardless of the value of the 'Transparent' spec.
- Fixed for 4.2.5.
Bug #1263: Auto totals printing erratically
- All the numbers in an auto subtotal are not always printing out. What is happening is that a random number of significant digits is being dropped starting with the rightmost character.
- Fixed under 4.2.5p21 client 4.2.4L 0-apps 4.2.5b4.
Bug #1264: LINEDRAW Widgets should not shrink to fit contents
- LINEDRAW widgets should be immune from the 'shrink to fit' feature. The widget editor should not allow editing of the 'shrink' field for a LINEDRAW widget.
- Fixed for 4.2.5.
Bug #1265: PDF Output not honoring appearance numbers
- In the General Ledger Trial Balance, when the total of all debits and credits is printed, the total Revenue + Expenses is also printed. They are individually built and displayed, but instead of both labels, only the second one prints, in both places.
- Fixed for 4.2.5. However, for now, you won't be able to use multiple appearances with text-area widgets. We'll fix this in a future release, but the fix is too far-reaching and dangerous for this release.
Bug #1266: Ratio Formula not printing
- In TGL 04, RATIOS PRINT, the formula isn't printing. There is a DISPLAY statement.
- Fixed for 4.2.5. (This is the same bug as #1265.)
Bug #1268: Range Totals don't honor sign space
- Range totals are no longer honoring the space for the plus sign. This makes positive number align one column too far to the right. (This is not a problem with the STANDARD SUBTOTAL output process.) The real bug is that right justified numeric fields are not preserving the trailing space when they have a trailing sign that is blank.
- Fixed for 4.2.5 client 4.2.4L 0-apps 4.2.5b4. The sign space is being honored but now the PDF reports have new problems as noted under Bug #1276.
Bug #1272: C-assert PDF end page: Unmatched save level
- This system error is encountered when attempting to run RTS 00 job CUSTOM PROSPECT LIST. The report can be run in text mode although there's not much to print other than row text.
- Fixed under 4.2.5.
Bug #1273: Stacked widgets no longer honor Transparent = Y
- Many reports still suffer from the stacked widget problem. The amount fields are now printing, but the logic fields are still not printing.
- Fixed in 4.2.5.
Bug #1278: Compression distorts boxes
Bug #1284: Label text is unexpectedly 'wrapping'
- Text that is being printed in a LABEL widget is unexpectedly being 'wrapped'. This can cause a text value to unexpectedly be printed as multiple lines if the horizontal size of the label allows it or this can cause the part of the text that won't fit to be discarded.
- Fixed as of 4.2.5. The separator line now prints and label text is now being clipped instead of wrapped.
Bug #1287: Vertical alignment of labels and data is off in PDF Output
- PDF Output does not vertically align labels and data properly. Have removed the float, all shrink values are null, and there is no compression, and vertical alignment is still off.
- Fixed for 4.2.5.
Bug #1288: Picture widget with shrink Null not printing on PDF Output
- A picture widget with shrink Null does not print on PDF Output. This is true even if there is no compression or float involved. The picture widget will print if shrink Neither is specified. Data picture widgets with shrink Null will print, however (as long as there is no compression).
- Fixed for 4.2.5.
Bug #1290: PDF Output hangs at runtime if PICTURE alpha item is blank
- If a PICTURE alpha item (defined with location type DESIGN) is blank, APPX hangs at runtime trying to print to PDF Output (this problem was originally reported in a comment under Bug #369).
- Fixed for 4.2.5.
Bug #1291: Compression suppresses PICTURE alpha items with shrink Null
- If PICTURE alpha items with shrink Null appear on a frame with a compress type other than NONE, the pictures do not print. The pictures do print if shrink is Neither or if compress type is NONE.
- Fixed under 4.2.5.
Bug #1292: Text Position of LABEL widgets behaving strangely
- Text positions LEFT, RIGHT, CENTER, BOTTOM, LOWER LEFT, and LOWER RIGHT are no longer honored and are printing as though specified UPPER LEFT, UPPER RIGHT, TOP, TOP, UPPER LEFT, and UPPER RIGHT respectively. It looks like they are being shrunk vertically. In addition, some borders are being shrunk horizontally.
- Fixed for 4.2.5. All text positions are now printing but some borders are being shrunk which is logged as Bug #1311. NOTE: there are some differences between what you see in the image editor and what you see in the PDF report. The Java client seems to be providing a default top margin for the widgets. Also, some of the boxes are resized to fit their content.
Bug #1295: PDF Output may not print some standard column headings
- If an output calls for standard column headings, some column headings may be missing in PDF Output. These headings do print in text output. Also, the standard column heading for a given field may print on another report.
- Fixed under 4.2.5.
Bug #1296: Some widgets not printing at all
- Some widgets are being dropped from printing entirely due to the effects of the 'shrink' parameter. For example, neither auto nor manual underscores or overscores print.
- Fixed in 4.2.5.
Bug #1298: Label widgets no longer honor right margin
- Label widgets no longer honor the right margin adjustment.
- Fixed in 4.2.5, but a new bug was introduced involving fill color. See Bug #1308.
Bug #1300: Numeric widgets with Text Position RIGHT not aligned properly
- PDF Output was not aligning right-justified numeric widgets with Text Position RIGHT with right-justified numeric items. It was only apparent when you print at 16.5 pitch. If you changed Text Position to null on the widget, then it is properly aligned.
- Fixed for 4.2.5.
Bug #1308: Fill color not filling label completely
- The fill color was not filling a label widget completely. Instead, if there was a margin defined, it filled only to the margin. This made the PDF forms look pretty funny.
- Fixed in 4.2.5.
Bug #1309: Data LABEL widgets do not print for some Text Positions
- An alpha label widget did not print for text positions LEFT, UPPER LEFT, and LOWER LEFT (similar to Bug #1292 for non-data label widgets). In addition to those, a numeric label widget with format 9(2) did not print for null text position.
- All text positions are now printing under 4.2.5., but some borders are being shrunk which is logged as Bug #1312.
Bug #1311: LABEL widget borders are shrunk for some text positions
- Borders are unexpectedly shrunk for label widgets with text positions LEFT, UPPER LEFT, and LOWER LEFT. This is despite the fact there is no compression or float involved on the frames.
- Fixed for 4.2.5.
Bug #1312: Data LABEL widget borders are shrunk for some text positions
- Borders are unexpectedly shrunk for data label widgets with text positions LEFT, UPPER LEFT, and LOWER LEFT. This is despite the fact there is no compression or float involved on the frames. In addition, the data items are defined with a Display Size for the original border.
- Fixed under 4.2.5.
Bug #1313: PDF Output may not print underscore character
- PDF Output does not seem to print the underscore character ' ' when used as a separator character on an image or when entered in the report subheading at runtime on the disposition screen. The underscore will print in both places on text output.
- Fixed for 4.2.5.
Bug #1317: PDF Output can distort Page-Start image if Page-Start has compression and widgets
- If a Page-Start frame has EMBEDDED or EMBEDDED/TRAILING compression, row text may be misplaced or vertical alignment of widgets may be off when the image prints.
- Fixed under 4.2.5.
Bug #1322: PDF Output may not float spaces properly (#1)
- If a label widget is followed by an alpha label widget with float, float may not be handled properly.
- Fixed under 4.2.5.
Bug #1323: PDF Output may not float spaces properly (#2)
- If a label widget (with shrink null) is followed by an alpha field with float, the float may not be honored properly. In an example, the alpha field called for floating 2 spaces. It looks like PDF Output allowed 2 spaces from the end of the label widget size, not the label widget text.
- Note that it is extremely difficult to size the label widget in order to provide the proper spacing yourself. This is due to the differences between what you see on the image and what you get in PDF Output (see Bug #1040).
- Duplicate of #1322 (the NULL shrink-to-fit spec in the leftmost widget causes the problem in both replication scenarios). Fixed for 4.2.5.
Bug #1324: Last frame on page duplicated
- Relating to Bug #366, now the final frame on each page is being duplicated (just the Window Properties, not the text).
- Fixed for 4.2.5.
Bug #1325: PDF Output can encounter C-assert 2100 using Float Spaces
- Encountered system error 'PDF save: Function must not be called in 'document' scope'. If you remove the Float Spaces specification from the alpha label widget, the job runs OK.
- This is identical to the one given in Bug #1323, except that Bug #1323 uses float on an alpha field, not an alpha label widget.
- The system error can be avoided if the Record frame has compression Trailing Blank Lines (and presumably anything but None).
- Fixed for 4.2.5.
Bug #1326: Tiling Mode = Expand no longer working
Bug #1331: PDF Output deletes row text following '<' sign
- PDF Output deleted row text following a '<' sign, including the '<' sign. If there was a '>' sign to the right on the same row, only row text up to and including the '>' sign was deleted and any remaining row text was shifted to the left. Otherwise, all row text to the right of the '<' sign on the line was deleted. Label widgets on the line were not affected.
- Fixed under 4.2.5.
Bug #1342: Float erratic on multiple fields
- If you have multiple fields floating on a subheading, the final float jams itself up against the neighboring field. See examples.
- Fixed for 4.2.5.
Bug #1350: PDF Output may not float spaces properly (##3)
- If Float Spaces are called for on a line, the spacing at print time can vary depending upon how widgets are sized and spaced on the image.
- Fixed under 4.2.5.
Bug #1351: Bar code does not work with 4.2.5
- Using code to 'fool' Appx by specifying font #10 in a widget using a barcode .ttf font in the Resource directory worked quite well in Release 4.2.4. The same output does not appear to work with early 4.2.5 releases.
- Fixed for 4.2.5.
Bug #1353: EMBEDDED compression has new problems under PDF Output
- If compression is Embedded, the totals print over the ='s which are on the line below the totals. This appears to be caused by the fact that one line is being compressed. If compression is None, everything is fine.
- Fixed in 4.2.5.
Bug #1364: PDF Box Label not Centered
- Formerly, a box on a PDF output form with a label that appears positioned in upper left or upper center was aligned vertically in the center of the letters of the label in DESIGN MODE, but was sitting ON TOP OF THE BOX when the actual output runs.
- Fixed for 4.2.5. NOTE: the box may obscure one letter of the associated text in both the upper left and upper right positions.
Runtime - Proc Compiler (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to Runtime - Proc Compiler
Bug #1348: Could not compile AT FIELD... if Appearance specified
- Using AT FIELD with the appearnce spec either using a --- integer PDF or a literal number. Would not compile.
- Fixed for 4.2.5.
System Administration (8 bugs)
Bugs Addressed in APPX 4.2.5 Relating to System Administration
Bug #52: Font spec on 'PDF' Form ignored by PDF output
- The font spec for a 'PDF' Form definition in System Admin was apparently ignored by PDF output.
- Fixed for 4.2.5.
Bug #707: Screens > 21 rows - Keymap Deletion
- When deleting a User, the second screen asked, "Do you want the related Keymaps deleted..."
- Fixed for 4.2.5.
Bug #715: Language menu: Building Dictionary needs stop sign
- The Building Dictionary process on the Language menu needs a status or a disposition so the operator has a chance to cancel it before it gets started.
- Fixed for 4.2.5 - A status process has been added to the job.
Bug #856: Screens > 21 rows - Documentation Rights
- The Documentation Rights screen only showed 6 modifiable lines in the scrolling area. Running with 36 rows, this looks like a lot of unused screen space.
- Fixed for 4.2.5 - The scrolling popup for documentation rights has been revised to be variable length. The scrolling popup for design rights has also been revised to be variable length. Design rights, Documentation Rights both now use a 'tall' screen.
Bug #1018: Spurious error message in Disposition at runtime
- With standard dispositions defined such that Print on Screen = Y and Print Hard Copy = N (for PDF output, since you choose that from Adobe Reader), and the option for background in, the Disposition input process gave no errors or warnings. But, at runtime, the first time the disposition screen comes up, it displays the error, 'Print On Screen Not Available In Background'. While that error message makes sense, it's not appropriate to show it there. And if you press Return to continue, it goes merrily on. The time to show that error message is if the user leaves Print on Screen = Y and tries to select Submit to Background. It wouldn't hurt to put a Warning in the Dispositions input process either.
- This is fixed in 4.2.5.
Bug #1330: Registration Screen not editable
Bug #1344: Inconsistent Default Mode
- System Administration inputs still start in Change Mode: Users, Printers, Forms, File System Groups, Disposition Definitions.
- Fixed for 4.2.5 - All file maintenance processes in System Administration now default to Inquire Mode when invoked.
Bug #1407: SysAdmin 'Copy to Clipboard' Has Wrong Verif Codes
- When using the new 'Copy to Clipboard' feature on the Version Info screen, the display of the verification codes for each licensed product displayed the first set of 4 digits five times, rather than the correct 20-digit verification code.
- Fixed for 4.2.5 to show the correct verification codes.
User interface (8 bugs)
Bugs Addressed in APPX 4.2.5 Relating to User interface
Bug #497: Print On Screen 'Title' Text Overlaps
- The Print On Screen 'Blue Title' had some overlapping fields. In particular, the Print? N overlaps the Report title. On a 'long' report title, the tile will appear on both sides of the 'Print? N'
- Fixed for 4.2.5 - The title bar only has room for the first 44 characters of the report title when running with a client size of 80 columns. So, there is the potential that the last 16 characters of the 60 character report title may get truncated.
Bug #727: Option Help - DISPOSITION
- Concerning --- Input DISPOSITION, there is little option help on this process:
- 1) Submit to BG - nothing
- 2) Load Settings - nothing
- 3) User Defined - nothing
- 4) Save Settings - 2 paragraphs
- 5) Cancel and Contine - nothing
- Also, No Tool Tips on any fields.
- Fixed for 4.2.5 - Added tooltips for all buttons; hid optional children; made Browsable a required field. All fields have help. All optional children have help.
Bug #737: Toolbar Tool Tips Do Not Show Key Board Equivalents
- The icons for Cancel, Add Mode, Change Mode, Inquire Mode, Delete Mode, and Acknowledge Delete are now 'Context Sensitive' (a great advance), BUT, the tool tip no longer gives the keyboard equivalent!
- Fixed for 4.2.5 - The tooltips for the standard toolbar buttons now include the corresponding direct access key sequence in parentheses.
Bug #767: Help Pop-Up Appearance - Full Screen versus Less than full
- Item Help looks VERY nice when not a full screen. The full screen version does not look nice in comparison.
- Fixed in 4.2.2.
Bug #774: Hard to Get Item Help - Impossible in Option 98
- It has alwyas been harder to get Item Help with the Java Client. In particular, in Inquire Mode and non-modifiable fields. The Java ? does not seem to get Item Help when the fields are non-modifiable! The mouse method seems to work well on a modifiable field.
- Fixed in 4.2.3
Bug #968: Help Screen on PRINT ON SCREEN
- While viewing a report on the screen, one can press F1 and see the Report Width in the lower right. This is handy to know how wide a report is and help select the approoriate form the next time the report is run. However, it appears that the Help area expands to match the report width. So, when > the display width, one needs to Pan right to see the Report width, but clicking the image closes the help!
- Fixed for 4.2.5 - The help screen for 'Print on Screen' should now be visible on all screen sizes >= 80 columns.
Bug #1094: New Undocumented Relations Appear in Record Selection
- The Record Selection Operators Drop-down now includes two new options: == and =~. These are not documented, and may not be functional.
- These are "regular expressions". You can find the documentation for regular expressions by typing: "$ man 7 regex" on any Linux box (and most Unix boxes).
- In 4.2.5, these have been changed from == =~ to RI and RS for 'Regex case Insensitive' and 'Regex case Sensitive'.
Bug #1299: appx print defaults to MPAGE on non-linux servers
- The appx print script is defaulting to an MPAGE filter on all unix systems. Linux is the only unix system that comes with mpage installed.
- Fixed in 4.2.5.
Winprint (1 bug)
Bugs Addressed in APPX 4.2.5 Relating to Winprint
Bug #513: Point size has different meanings depending on platform
- The meaning of the '-pitch' parameter is different, depending on if you print on a Linux/Unix box or a Windows box.
- This problem has been around for a long time. winprint treats pitch as if it were point size. mpage treats pitch as cpi. So, pitch=12 will print 12cpi using mpage and will print a point size of 12 when printing via winprint.
- Fixed for 4.2.5 - We have added a new option for winprint called '-point'. With this release, '-point' and '-pitch' both are interpreted as point size. In a future release, we will change the interpretation of '-pitch' to be the same as cpi (characters per inch). So, with this release, all users should revise any existing Windows form definitions to use '-point' to specify point size.
New Widget Attribute - Shrink to Fit Content
- <null> - Let APPX decide if the widget should shrink horizontally and/or vertically.
- HORIZONTAL - Shrink the widget horizontally from right to left.
- VERTICAL - Shrink the widget vertically from the bottom to the top.
- BOTH - Shrink the widget both horizontally and vertically.
- NEITHER - Do not modify the defined size of the widget.
Behavior
A box widget is never shrunk so this new attribute does not apply.
Only widgets that have <null> or LEFT justification of the contents can be shrunk.
If a widget has no contents, it will effectively "disappear" if shrunk.
Known Bug - Appearances in PDF Output
Microsoft, Windows, Windows Server, Windows Server 2000, Windows Server 2003, Windows Vista, Windows XP,Windows 7, Microsoft SQL Server and Microsoft Access are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
APPX 4.2.4
The APPX 4.2.4 Patch Release addresses the following items:
- Bug #731: Client Preferences issues
- Bug #996: File Names not available to scan from READ stmt
- Bug #998: GUI destroys field content if multiple '=' characters are contained
- Bug #1023: Spelling mistake in DD
- Bug #1026: Scan fails with seg fault
- Bug #1027: License server off by one
- Bug #1028: Multiple sessions not allowed after registration limit reached
- Bug #1034: Maintenance agreement license server changes
- Bug #1036: Scan on Alternate key returns 1st record
- Bug #1037: Direct Process 1 = > Signal Error
- Bug #1066: Scan doesn't return 1st record when <Enter> is pressed
- Bug #1079: Overriding LOGIC field as BIT field doesn't work
- Bug #1087: 0-apps cursor in wrong place
Bug #731: Client Preferences issues
- There were differences between value and default value for debugNotifyLevel and debugLogLevel caused by one being the token value, the other the token number. Also, widget is misspelled in the description for editorForceSize.
- These have been corrected.
Bug #996 - File Names not available to scan from READ stmt
- When entering a READ statement and scanning to select the file name to be read, only field names were presented, and the 'Select File' option button does not function.
- Corrected as follows: When you scan on an operand that can contain a field name or a file name, you should now be able to scan for either. The scan processor will show you the list of files by default - use option 1 to scan fields instead. The scan processor will remember your scan preference.
Bug #998: GUI destroys field content if multiple '=' characters are contained
- If the content of an alpha field is a series of '=' characters (example '==========') the gui represented its content as NULL (empty). If the record was stored the field content was blanked out. If the alpha field contained a substring of '=====' 's that substring was replaced by blank characters.
- This has been fixed.
Bug #1023 - Spelling mistake in DD
- In the AA popup for Alpha fields, the 'Lowercase OK?' label is misspelled as 'Lowercare'.
- This has been corrected.
Bug #1026 - Scan fails with seg fault
- Invoking scan from within a live application caused a seg fault.
- This has been fixed.
Bug #1027 - License server off by one
- The Appx license server granted one too many usage rights for any counted feature registrations.
- This has been corrected.
Bug #1028 - Multiple sessions not allowed after registration limit reached
- The license server, which allows up to four logins under the same user ID for each usage right, disabled multi-session logins once you reached the maximum number of users allowed by the registration.
- This has been corrected.
Bug #1034 - Maintenance agreement license server changes
- The Appx license server previously compared the expiration date contained in the APX/MNT feature registration with the compile date of the Appx engine. If the engine was built after the registration expiration date, Appx reported an invalid, missing or expired MNT registration.
- Our new maintenance policy states that a user can run any patches made to a supported version of Appx. In other words, if version 4.2 (a major release) is released while your APX/MNT registration is valid, you should be able to run any 4.2.x release, even if 4.2.x was issued after your APX/MNT registration has expired.
- This feature has been implemented in 4.2.4.
Bug #1036 - Scan on Alternate key returns 1st record
- When you did a scan on Alternate key and select a record from a list built by that scan, it returned the first record from that list.
- However, if you scanned on the Primary Key first and changed path to Alternate Key, 'select' works properly.
- This has been fixed.
Bug #1037 - Direct Process 1 = > Signal Error
- When user defined a SYSPARM Direct Process 1, users entering appx got => MODULE: BI.C.1727 ; 'An unrecoverable error has occurred (signal), exiting'
- This has been fixed.
Bug #1066 - Scan doesn't return 1st record when <Enter> is pressed
- When scanning a file, if the desired record is the first one on the screen, a simple return did NOT bring the record back. Only by clicking on the record would it be retrieved.
- This has been fixed.
Bug #1079 - Overriding LOGIC field as BIT field doesn't work
- When overriding the LOGIC fields to BIT data type, a problem is detected with the inputs. The Checkboxes always appeared UNCHECKED (if seen from the Java Client) and when checked the values didn't seem to work properly in SQL Server. Leaving the fields as varchar(1) was the best method to handle this error.
- This has been corrected.
Bug #1087 - 0-apps cursor in wrong place
- When adding records on a scrolling display, when you reached the bottom of the display and added a record, after returning to the scrolling display, the cursor was on the row above the bottom row.
- This has been corrected.
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release. Also refer to the Release Notes for APPX 4.2.1, APPX 4.2.2, and APPX 4.2.3 for items addressed by those patch releases.
APPX 4.2.3
The APPX 4.2.3 Patch Release addresses the following items:
- Bug # 93: Toolbox is not accessible from Data Dictionary
- Bug #272: F8 sometimes won't end Main Menu
- Bug #358: REFRESH statement does not send widgets to client
- Bug #383: Cosmetic Query Process Level display bug
- Bug #422: --- STREAM CLOSE returns failure for 'pipe' stream
- Bug #427: Java Client 0AD Tools and Utilites Menu Process pulldown needs work
- Bug #437: Java 0AD File Design level has no Toolbox button
- Bug #447: File Chooser steps on field contents during folder drill down
- Bug #548: ILF Search & Replace fails on KEY portions of I/O commands
- Bug #564: Some 0AD Process PullDown descriptions are less-than-perfect
- Bug #577: Current Query Des. Sel. Rel. hidden by SCAN indicator in ADD/CHG
- Bug #660: GUI Title Bar disappears
- Bug #678: Image Editor Item Display (F11) needs Page X of Y as per java client
- Bug #732: Full re-install of JC b9 over writes some Advanced options in .ini
- Bug #743: AppxdSvc Always Logs
- Bug #760: Tabbing through multi-row fields requires hitting tab twice
- Bug #774: Hard to Get Item Help - Impossible in Option 98
- Bug #784: Keyboard Buffer does not work
- Bug #802: Convert Images Utility is virtually useless
- Bug #804: CNV PORT is missing from ILF Editor Statement SCAN
- Bug #835: 'This record already held by another user' unexpectedly encountered
- Bug #837: Output Image Editor displays row of = 's as gray bar
- Bug #842: DD Toolbox Missing 'Convert to Domain' & 'Copy'
- Bug #851: 30 column scan fails
- Bug #863: REWRITE statement returns T but doesn't really rewrite
- Bug #882: 0SA APPL ALLOW DESIGN - No longer works
- Bug #884: REFRESH TEMP 80 is broken
- Bug #891: Focus remains on date chooser button
- Bug #892: FLEP Problem with Cache Priority 1
- Bug #898: Using a cached file as the PCF can cause crashes
- Bug #906: Mod logs don't display occurrences correctly
- Bug #907: Mod logs show deleted record values in wrong column
- Bug #914: Scanning on field name too restrictive
- Bug #915: 'guilook' defaults differently, can't change it.
- Bug #925: End of Process (Query Setup) EP does not always run
- Bug #930: Access to Designer Rights
- Bug #934: Constrained Read silently skips records
- Bug #935: Date Chooser Returns Blank Date
- Bug #947: HELP loses changes if you edit twice
- Bug #950: REFRESH TEMP 80 in Output aborts Output
- Bug #963: Can't select by keyboard on single-field-display file scans
- Bug #975: RESTORE statement hangs if scanning on 'DEFAULT RECORD' field
- Bug #976: F1-F12 not working on text fields
- Bug #978: -windowTitle= command line argument ignored
- Bug #997: PgUp and PgDn in SCAN for Process Name oversteps processes
- Bug #998: GUI destroys alpha field content if multiple '= ' characters are contained
- Bug #1006: Print On Screen - Option 7 No longer works
- Task #111: Implement new Unix/Linux Connection Manager
Bug # 93: Toolbox is not accessible from Data Dictionary
- The Data Dictionary toolbox, which contained such utilities as "Convert Field to Domain" and "Copy Fields", was not visually accessible. This has been fixed.
Bug #272: F8 sometimes won't end Main Menu
- It was sometimes necessary to click on "Exit" from the APPX Main Menu, rather than just pressing F8 (or ESC), to exit APPX. This has been fixed, as part of the major reworking of keyboard handling for type-ahead issues.
Bug #358: REFRESH statement does not send widgets to client
- When a REFRESH statement was executed, field values were being sent to the screen but widget records were not. This has been fixed.
Bug #383: Cosmetic Query Process Level display bug
- The first two records of the Query Process scrolling image appeared 'within' the box of the header frame.
- This has been fixed.
Bug #422: --- STREAM CLOSE returns failure for 'pipe' stream
- This has been fixed.
Bug #427: Java Client 0AD Tools and Utilites Menu Process pulldown needs work
- The 'Utilites' and especially the 'Tools' menus contained enough optional children that having a Group specification of the Optional Child label would not be a luxury.
- This has been fixed.
Bug #437: Java 0AD File Design level has no Toolbox button
- Toolbox was accessible only through opt-1
- This has been fixed.
Bug #447: File Chooser steps on field contents during folder drill down
- This has been fixed.
Bug #548: ILF Search & Replace fails on KEY portions of I/O commands
- ILF Editor didn't find values in the key space of a READ, READNEXT, or BEG READ statements.
- User also couldn't manually change those values when in his ILF Search&Replace.
- Search & Replace also failed on the right side of an IF statement, but that could be manually corrected, and the Search & Replace continued.
- This only seemed to happen when the 'new' string is shorter that the 'old'.
- This has been fixed.
Bug #564: Some 0AD Process PullDown descriptions are less-than-perfect
- Documentation Process Pulldown : 'Summary' and 'Detailed' presumably refer to Domains
- This has been fixed.
Bug #577: Current Query Des. Sel. Rel. hidden by SCAN indicator in ADD/CHG
- There was about one cell too little allowed for the 'Rel' in this scrolling display.
- This has been corrected.
Bug #660: GUI Title Bar disappears
- An INPUT process' Frame-Size-Rows of less than the default of 21, caused the GUI (Window Properties) Titlebar-Options 'Title' attribute to not display a titlebar at runtime. This has been fixed in Java client release 4.2.2c.
Bug #678: Image Editor Item Display (F11) needs Page X of Y as per java client
- (From Bruce Johnston:) I was going to complain that the scroll bar doesn't appear on the displayed frame until I remembered that it's NOT a scrolling window but rather a display with 10 modifiable occ. of the info on each line.
- No need to complain - it has been fixed.
Bug #732: Full re-install of JC b9 over writes some Advanced options in .ini
- After a full uninstall and re-install, the caret color, which had been set to red, went back to black even though other default in the .ini retained my custom values.
- This has been fixed.
Bug #743 - AppxdSvc Always Logs
- You can adjust the logging parameters by setting three registry values:
LogServiceDir - set to the name of a directory and AppxDSvc will write the log there (in a file named $(LogServiceDir)serviceName.log - LogAllEvents - set to 'Y' to get a complete log or any other value to disable most log messages. The default is 'N' so you should be seeing very few message written to the log
- LogCreate - set to 'Y' to create a log file or any other value to disable logging. The default is 'N' (starting with 4.2.3 - it defaulted to 'Y' before release 4.2.3).
Bug #760: Tabbing through multi-row fields requires hitting tab twice
- If tabbing to different fields on an input and you came to a text or alpha field that had multiple rows, you had to hit the tab button twice to get to the next field. This has been fixed in Java client release 4.2.2c.
Bug #774: Hard to Get Item Help - Impossible in Option 98
- It has alwyas been harder to get Item Help with the Java Client. In particular, in Inquire Mode and non-modifiable fields.
- Bug 1 - The Java ? does not seem to get Item Help when the fields are non-modifiable! The mouse method seems to work well on a modifiable field.
- Bug 2 - The work around, Turn off GUI Interface, still works on a simple scroller, but when you pop Audit Info (you can see this in the Process scroller) you cannot get the cursor over to a field to get Help!!
- The prior work around was to exit the GUI Mode and move the cursor around; that did not work any more!
- This has been fixed.
Bug #784: Keyboard Buffer does not work
- The old keyboard buffering problems have resurfaced. Looks like there is no keyboard buffered at all; typing very fast, lots of keystroke after each other, results in loss of arbitrary keystrokes...
- This has been tightened up significantly for 4.2.3. Please report any new instances as new bugs.
Bug #802: Convert Images Utility is virtually useless
- When you attempt to Convert Images, APPX requires that the target exist. Does this mean that I have to create all of my output processes first with dummy target images in order to be able to use this utility?
- Corrected in 4.2.3.
Bug #804: CNV PORT is missing from ILF Editor Statement SCAN
- This has been fixed.
Bug #835: 'This record already held by another user' unexpectedly encountered
- This occurred only in the DISAM environment
-
When returning to the parent process from the child process, APPX encounters the following errors:
- ERROR - Record Not in File
- This record already held by another user
- When running with APPXIO instead of DISAM, these errors are not encountered. There were no other users or sessions running the same database.
- This has been fixed.
Bug #837: Output Image Editor displays row of = 's as gray bar
- A row of equal signs should display as such at design time, not as a gray bar (which is an auto-GUI feature at runtime for an input). It does print as a row of equal signs.
- This has been fixed.
Bug #842: DD Toolbox Missing 'Convert to Domain' & 'Copy'
- The toolbox options to convert a field to a domain and to copy fields are not available on the menu bar or buttons in the data dictionary.
- Fixed for 4.2.3.
Bug #851: 30 column scan fails
- When scanning on a field that uses NSCAN (30) the user receives an Appx ILF error on a DEFINE statement for --- ENTRY KEY FLD VAL ZI. This has been fixed.
Bug #863: REWRITE statement returns T but doesn't really rewrite
- This occurred only in the DISAM environment.
- REWRITE of PCF record in 'footer' frame of update process returns a T indicating success but the record is not really rewritten.
- This has been fixed.
Bug #882: 0SA APPL ALLOW DESIGN - No longer works
- In 4.2.2 the new feature allowing changing of modes at lower levels allowed changes to the design as well at lower level despite the setting of the 0SA APPL ALLOW DESIGN field!
- The application chooser now shows a READONLY icon in the left column of the scrolling display for applications that are locked from changes due to the Application 'Allow Design?' flag.
Bug #884: REFRESH TEMP 80 is broken
- This is fixed in 4.2.3 client.
Bug #891: Focus remains on date chooser button
- After using the date chooser button to select a date, the cursor focus remained on the button on returning to the input image. If the user then pressed RETURN, the date chooser popup box re-appeared rather than the expected result (i.e. processing of the RETURN option by the image). Even if the user didn't press RETURN, the cursor focus was not obvious to the user.
- This is fixed in 4.2.3 client.
Bug #892: FLEP Problem with Cache Priority 1
- When the cache priority was 1 when a new sessions starts, FLEP's didn't fire for the process. This was reported specifically happening in a Job with the first step being a Query. If the cache priority was changed, the FLEP's fired. If the cache priority was changed from 2-99 to 1, the FLEP's fire as expected. This only seemed to occur if the cache priority was initially set to 1 when the session started.
- For the record, this bug would only occur when a query process EM gets tossed out of the cache and is subsequently read back in. In the replication scenario, the query setup job step loads the query EM into memory, the next job step throws the query EM out of cache, and then the 'use query' job step loads the EM again.
- You could replicate this bug at priorities other than one, but it's not easy and depends on your USER CACHE LEVEL and which other EM's are in the cache.
- Fixed in 4.2.3.
Bug #898: Using a cached file as the PCF can cause crashes
- Using a cached file as the PCF for a scrolling input process could cause various crashes. You would have to use an OPEN or CREATE stmt. in the Start-of-process event point for this problem to appear.
- The symptom varied - on a Windows® platform, the appx.stk file grows for a very, very long time. On a Linux/Unix platform, you could see a huge number of [defunct] processes spawned by the engine when the error occurs.
- This has been fixed.
Bug #906: Mod logs don't display occurrences correctly
- If the PCF for a process contained any multi-occurrence fields, the modification log entries for a CHANGE operation were incorrect. The mod log seemed to skip every other occurrence, and the values shown were associated with the wrong occurrence numbers.
- This has been fixed.
Bug #907: Mod logs show deleted record values in wrong column
- The modification log entries generated for a DELETE showed the PCF values in the 'New' column instead of in the 'Old' column.
- This has been fixed.
Bug #914: Scanning on field name too restrictive
- When scanning on the source field name of an APPEND statement, the scan list did not include ALPHA fields that are defined by DOMAINS.
- Fixed for 4.2.3.
Bug #915: 'guilook' defaults differently, can't change it
- The 'guilook' parameter defaulted differently. It used to default to 'appx', but now defaulted to something else (java?). Even worse, you couldn't force it to what you wanted by specifiying it on the command line.
- This is fixed in the 4.2.3 client.
Bug #925: End of Process (Query Setup) EP does not always run
- If a query was executed with first having executed a QUERY step in the job, the End of Process (Query Setup) EP does not run. The Start of Process (Query Setup) EP does run.
- This has been fixed.
Bug #930: Access to Designer Rights
- Even though the message 'ERROR - No Application Designer Rights' was displayed, user was able to go to change mode and make changes to an application that was manually keyed in on the App Chooser screen.
- This has been fixed.
Bug #934: Constrained Read silently skips records
- NOTE: This was originally reported as just a problem with BEG READ/END READ, but in fact it happens with any kind of child constraint.
- If task 'A' has a hold on a record in file 1 (but not the first record) and task 'B' is doing a constrained Read with Hold on the same file (e.g., an UPDATE with child constraints), the record held by the other task would be completely skipped by the Read, with no warning, error or held condition indicated.
- The problem did not occur if the first record is held, or if the BEG AT/END AT is unconstrained.
- This is similar to ECR 5166 and 662, except those reference using an Alternate key. We have found that this occurred even when using the primary key.
- This was a fairly serious problem, as the Designer could no longer count on a constrained READ to read all the records with Hold in a multi user environment. This could cause all kinds of subtle application errors, e.g., orphan records, etc.
- Fixed for 4.2.3 - Appx will now wait for locked records rather than silently skipping them
Bug #935: Date Chooser Returns Blank Date
- Clicking on the Date Chooser Icon returned a blank date.
- This has been fixed for the 4.2.3 Java client.
Bug #947: HELP loses changes if you edit twice
- If you are a System Administrator or Designer/Documentor, you can edit the Help text on the fly.
- User edited one, pressed enter to redisplay, was not content with the edits, and pressed F12 again. The first edit was lost; it reverted to the pre-edit state.
- This has been fixed in the 4.2.3 0-apps.
Bug #950: REFRESH TEMP 80 in Output aborts Output
- In the Pre-Display EP of a record frame of an output process, the command "REFRESH TEMP 80" aborted the Output, sending it to the End of Process Event Point, the second time the statement was executed.
- This has been fixed in 4.2.3.
Bug #963: Can't select by keyboard on single-field-display file scans
- When scanning on a data lookup into a file for which only one field is defined as displayable, selecting with the mouse brought back the desired record, but trying to select by using cursor arrow keys and ENTER brought back no result at all.
- This has been fixed in the 4.2.3 client.
Bug #975: RESTORE statement hangs if scanning on 'DEFAULT RECORD' field
- In the ILF editor, when adding a RESTORE statement, tab to the last field (where you would to enter DEFAULT RECORD) in order to pick 'DEFAULT RECORD' from the scan list, and press F2. APPX hangs.
- This has been fixed in the 4.2.3 client patch.
Bug #976: F1-F12 not working on text fields
- F1-F12 were not working when cursor is positioned on a text field.
- This has been fixed in the 4.2.3 client.
Bug #978: -windowTitle= command line argument ignored
- Setting the startup option for -title= or -windowTitle= is ignored.
- This has been fixed in the 4.2.3 client.
Bug #997: PgUp and PgDn in SCAN for Process Name oversteps processes
- When scanning for a process name (e.g., in design transfer), pressing PageUp or PageDown scrolled more than one page. Therefore not all processes were visible.
- This may be because there is less than a full page of processes visible, and the PgDown scrolls for a full page.
- This has been fixed for 4.2.3.
Bug #998: GUI destroys alpha field content if multiple '= ' characters are contained
- If the content of an alpha field was a series of '=' characters ('========'), the GUI represented its content as NULL (empty). If the record was stored, the field content was blanked out. If the alpha field contained a substring of '=====' characters, that substring was replaced by blank characters.
- Fixed for 4.2.3.
Bug #1006: Print On Screen - Option 7 No longer works
- Option 7 to email a report, when a report was brought to the screen, was no longer working.
- This has been fixed in 4.2.3.
Task #111: Implement new Unix/Linux Connection Manager
- Implement a new connection manager (uappxd) for Unix/Linux systems that provides for easier installation and configuration and includes new features.
- This new feature is included in APPX 4.2.3 on an "experimental" basis. User feedback is welcome.
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release. Also refer to the APPX 4.2.1 Release Notes and APPX 4.2.2 Release Notes for items addressed by those patch releases.
Microsoft, Windows, Windows Server, Windows 2000, Windows Server 2000, Windows Server 2003, Windows 98, Windows NT 4, Internet Explorer, Windows Vista, Windows XP, Windows 7, Microsoft SQL Server, Microsoft Access and Microsoft Excel are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
APPX 4.2.2
The APPX 4.2.2 Patch Release addresses the following items:
- Bug #838: SCAN is not Hookable
- Bug #833: Client needs more control over Screen Fonts
- Bug #829: PDF Reports fail on RISC platforms
- Bug #821: 0LC - Hookable Processes HELP
- Bug #817: Duplicated Toolbar AutoGui Buttons
- Bug #810: DISAM restructure fails across file systems
- Bug #755: Changing modes trips error in Pre-Display/Verify
- Bug #673: Blank line generated before separator line in page heading
- Bug #669: Designer has no control over separator character
- Bug #640: Separator character overwritten
- Bug #617: PDF Output encounters c-assert if no records selected
- Bug #517: PDF Output encounters c-assert if output has only a PAGE-START frame
Bug #838: SCAN is not Hookable
- The 0LA Input processes are in 0LC to be copied and hooked. These are now hookable under 4.2.2. The list of input processes that make up the SCAN process family are:
- NSCAN
- NSCAN (110)
- NSCAN (125)
- NSCAN (30)
- NSCAN (35)
- NSCAN (50)
- NSCAN (65)
- NSCAN (80)
- NSCAN (TOKEN) (15)
- NSCAN (TOKEN) (35)
- NSCAN FILE SELECT
- NSCAN KEY VALUE
- NSCAN PATH SELECT
Bug #833: Client needs more control over Screen Fonts
- The -font= setting will let you use any OS or Java font as the base font used to compute all the screen geometry. 'fixed' and 'prop' are just shortcuts to reference 'Courier' and 'Helvetica'. In the prior versions of the client, Courier on linux really used a font called 'Lucida Sans Typewriter'. That was because of the way the Sun Java 1.2 and 1.3 VMs handled font names.
- We now use Sun Java 1.4 which does honor Courier. So, if Courier is really not what you want, you should use a different real OS font name.
- The list of available font names could be different on every system. So, the help with this the 4.2.2 client will dump the list of available fonts on a given system to the appxlog.txt file. It will also present a dropdown list in the Advanced Properties table of all the currently available OS fonts.
Bug #829: PDF Reports fail on RISC platforms
- A report that utilizes standard page or standard column headings will fail if printed as a PDF-formatted report, but only on RISC platforms. This has been fixed.
Bug #821: 0LC - Hookable Processes HELP
- When I Design transfer 0LC HELP and hook the process, I get an error:
Invalid Application ID
- Offending code, per the EM Build Error Listing is:
Frame: Image: Child: START OF PROCESSWRITE 0AD DOCUMENT
- This has been fixed.
Bug #817: Duplicated Toolbar AutoGui Buttons
- Sometimes the OK and Cancel buttons that show up on the toolbar are repeated 2 or three times on the toolbar. These are the buttons generated by the AutoGui STANDARD TOOLBARS process. It seems to be caused by having Direct Process 1 and/or Direct Process 2 active. This has been fixed.
Bug #810: DISAM restructure fails across file systems
- If you restructure a DISAM file that is located in a different file system than the restructure work directory (Newdata), then the restructure will indicated that it ran successfully but the file will be missing. This has been fixed.
Bug #755: Changing modes trips error in Pre-Display/Verify
- If an input process defaults to Inquire Mode, and you hit F12 to use Change Mode for key entry, it trips an error in my application in Pre-Display/Verify (looking to see if a field is blank). This has been fixed.
Bug #673: Blank line generated before separator line in page heading
- If you specify a separator character, there is a blank line generated before the separator line. The only time it does not appear seems to be when there is no Page-Start frame. You get the blank line if there is a Page-Start frame even if you suppress printing by setting alternate image number to 0. This has been fixed.
Bug #669: Designer has no control over separator character
- No matter what character you specify for the separator line (as long as it's non-blank), it prints as sort of a double underline character. This has been fixed.
Bug #640: Separator character overwritten
- In the situation where a designer has requested standard column headings but has also designed a Page-Start frame, the separator character can get overwritten by the first line of data, and the designer-specified image is also overwritten by the GUI page heading. This has been fixed.
Bug #617: PDF Output encounters c-assert if no records selected
- C-Assert: PDF_begin_page: Function must not be called in 'page' scope. This has been fixed.
Bug #517: PDF Output encounters c-assert if output has only a PAGE-START frame
- C-Assert: PDF_begin_page: Function must not be called in 'page' scope. This has been fixed.
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release. Also refer to the APPX 4.2.1 Release Notes for items addressed by that patch release.
APPX 4.2.1
The APPX 4.2.1 Patch Release addresses the following items:
- Bug 754: Design Transfer hangs on third Transfer
- Bug 803: APPX_PRINT on Unix doesn't spool to Unique properly
- Bug 807: Background Processing Fails
- Bug 808: PRINT FILE PATHNAME corrupted
- Bug 815: No "Acknowledge Delete" button for work fields
- Task 17: APPX_USAGE_BITS needs another one just for Session End
Bug 754: Design Transfer hangs on third Transfer
- Running Design Transfer several times in a row and scanning for the "From" process name each time caused a lockup on the third Scan operation. This has been fixed.
Bug 803: APPX_PRINT on Unix doesn't spool to Unique properly
- When spooling to Unique via appx_print, nothing gets into the Unique print queue. This is because the print file is deleted by appx_print before Unique can print it. We now don't delete the print file, we leave it there for unique to delete.
Bug 807: Background Processing Fails
- Background processing fails 100% of the time. Usage log shows 'Appx System Error (BI.C:1714) - An unrecoverable error has occurred (signal), exiting'. Background processing works again.
Bug 808: PRINT FILE PATHNAME corrupted
- The value of --- PRINT FILE PATHNAME has changed with 4.2 so that it now has a null 0x00 appended immediately after the pathname. All code that uses PRINT FILE PATHNAME as part of a RUN string now fails since the RUN string is truncated on execution at the 0x00. This has been fixed so that PRINT FILE PATHNAME works as it always has in the past.
Bug 815: No "Acknowledge Delete" button for work fields
- In Work Fields maintenance, in delete mode, there is no Ack Delete button on the screen. This has been fixed.
Task 17: APPX_USAGE_BITS needs another one just for Session End
- Under a minimal surveilance scheme I'd like to simply log the session start and end. Currently you can get the session start by itself by simply setting APPX_USAGE_BITS to 0x80000000. You won't get any end info unless you also set the lowest bit. Then you get every process that you ever run in addtion to the END of the first process that you executed when you started you APPX session. Should be fixed in 4.2.1 - use bit 0x200 to see session start and session end log entries
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release.
APPX 4.2.0
The Release Notes for APPX 4.2.0 are presented in sections. Please click on the section below to view the corresponding release notes.
Installation
O/S Issues
Initial Setup (Operational Phase)
Run-Time Environment
Run-Time Behaviors
System Administration
Application Design
Database Management
FMS Interfaces
APPX GUI Client
Reportwriter (SQL)
Installation
General
Operating System Versions Required
- Risc Processors:
IBM RS/6000 - AIX 4.3.3 & higher
HP - HPUX 11.0 & higher
SUN (Sparc) - Solaris 8; SunOS 5.8 & higher
- Intel & Intel Compatible Processors:
Linux - Redhat 7.2 & higher
Linux - Redhat Enterprise Server 2.1 & higher
Windows® - Windows 98®, Windows NT 4®, Windows 2000®, Windows Server 2003®
NCR SRV4 MP-RAS Version/Release 03.02.00.39
SCO OpenServer Enterprise System (ver 5.0.4p)
DG/UX R4.20
RDBMS/FMS Versions Supported
- Oracle 9i (9.2.0) - APPX 4.2.0 has been tested with Oracle 9i and has been dynamically linked with the Oracle 9 Client Software. Oracle customers who desire to run Oracle 7 or Oracle 8 with APPX 4.2.0 should check with Oracle regarding compatibility of Oracle 7 and Oracle 8 with the Oracle 9 Client Software.
- DB2 (7.1)
- ODBC (3.0)
- DISAM96 (6.12) - Replaces C-ISAM
- Sybase - The APPX/Sybase interface may no longer be purchased. However, the existing Sybase interface will be retained in this release so that existing Sybase customers may migrate to our ODBC interface.
- Vision - The APPX/Vision interface may no longer be purchased. However, the existing Vision interface will be retained in this release so that existing Vision customers may migrate to our ODBC interface.
Registration import utility improved
- The registration import step that is run as part of "finalizing" a new installation has been modified to be more understandable and intuitive.
Windows
AppxdSvc replaces WinAppxD
- The "winAppxD" Connection Manager has been replaced by a new "appxdSvc" Connection Manager. The new Connection Manager is a "true" Windows service and is much easier to install, configure, and control. It's also more immune to denial-of-service attacks. The new Connection Manager also supports multiple authentication methods: you can, if you choose, configure appxdSvc to validate passwords against the Appx password file rather than the OS password file. That means that you can control the passwords more easily. It also means that you do not have to create an OS account for every Appx user.
O/S Issues
Security on Directories
appx_print can't create log file in /tmp - ECR Number 6679
- Printing under Appx for Unix no longer fails with "/tmp/appx_print.last: cannot create" messages due to undeleted files, due to the "t" in newer OS's /tmp 'drwxrwxrwt' directory permissions.
Initial Setup (Operational Phase)
Input Processes
Fields should not be modifiable in INQ - ECR Number 6804
- In Operational Phase INITIAL SETUP when running an Input process in INQUIRE mode, fields with blank "Modifiable?" attributes were unexpectedly modifiable.
Run-Time Environment
C-Asserts
More info on mm_alloc panic out of mem - ECR Number 6832
Display on Screen
Panning now works for client cols > 80 - ECR Number 6806
Help
Boxes now drawn around all sizes of help - ECR Number 6805
License Server
Application Locks not being released - ECR Number 6865
Print Disposition
PDF output can be generated on client or server
Warning on disposition if PDF form type
PDF printing on local and server printers
Run-Time Behaviors
-
APPXIO
-
File Level Event Points
-
General
-
ILF Statements
-
Input Processes
-
KEATERM
-
Language Translation
-
Output Processes
-
Query Processes
-
Subroutines
APPXIO
Enable large-file support for Linux - ECR Number 6905
REWRITE of consec record loses position - ECR Number 6883
REWRITE without HOLD could corrupt file - ECR Number 6816
SCRATCH fails if structure file missing - ECR Number 6838
File Level Event Points
SCRATCH followed by DELETE breaks FLEPs - ECR Number 6171
- File level event points were improperly disabled for files SCRATCH'ed and CREATE'd with ILF.
- The presence of SCRATCH & CREATE in an INPUT or OUTPUT's Start-of-Process Event Point disabled most (but not all) File Level Event Point firing
- PCF files' FLEP would fail to fire in Start-of-Process, if Start-of-Process SCRATCH'ed and CREATE'd the PCF file.
- Non-PCF FLEPs were disabled if the file had SCRATCH and CREATE verbs in the OUTPUT process' Start-of-Process.
- FLEPs now work correctly when the underlying file is SCRATCH'ed and CREATE'd.
General
All screens should be GUI-fied
Implement '+' mask character for numeric - ECR Number 6904
Toolbar button size selectable at runtim
ILF Statements
CNV TEXT behavior changed - ECR Number 6897
- CNV TEXT on a Record or GROUP HEADER converts multiple component fields on the Right Hand Side of the statement into a single LHS alpha field. (Option/88 allows saving of File Names on the RHS of CNV TEXT statements.)
- Multiple component fields on the RHS are known as a "Composite Reference". A CNV TEXT is generated for each component field, converting each field into its mask's alpha format. CNV TEXT then strings them together.
- In 4.1, specifying a GROUP HEADER field isn't considered a composite reference, so you don't get a field by field conversion. It treats GROUP HEADERs as one long alpha field.
- To CNV TEXT in the reverse direction (converting a LHS alpha field back into its component fields), you may want to use a separate file as an interim CNV TEXT work area, so that you don't have to consider spacing between fields, etc.
COMPUTE statement results in wrong sign - ECR Number 6829
Inquire mode honors errors and warnings
Input Processes
ADD mode scrolling prob for consec PCF - ECR Number 1825
ENABLE/DISABLE now apply to mult widgets - ECR Number 6899
ERROR stmts are now honored in INQ mode - ECR Number 4126
- Prior to 4.2, Input process in INQUIRE mode ignored ERROR and WARNING statements. INQUIRE mode now honors ERROR and WARNING statements.
- (To revert to the prior behavior, set environment variable: APPX_SUPPRESS_INQUIRE_ERRORS=1, causing Appx to revert to the 4.1 behavior. This variable will not be included in future releases. We strongly recommend changing your ILF code if you want to suppress ERROR and WARNING messages in INQUIRE mode in your own applications.)
Mode change for one-record inputs
Mode change retains key on form inputs
Parent PCF record now reread in INQ mode - ECR Number 5772
- When an Input process invokes an optional child, the parent process re-reads its PCF record (with hold) after the child process completes.
- Prior to release 4.2, the re-read only occurred if --- INTERACTIVE PHASE equaled DATA MODIFICATION, which it would do if the parent was in Change or Add mode when it invoked the child.
- As of 4.2, the parent process also re-reads the PCF record (without hold) when --- INTERACTIVE PHASE equals DATA INQUIRE, which it does if the parent was in Inquire Mode when it invoked the child, or if the parent was in Change Mode, but the parent record became held by another user.
Pre-Display EP's now execute after child - ECR Number 6308
- We changed the event point sequence when the user selects option USER 0 through USER 255. Previously, Appx would not execute the Pre-Display and Pre-Display/Verify event points after returning from an optional child. Now when you return from an optional child, Appx ends the current image and reinvokes it.
- This means that programmatic updates of GUI attributes (by updating --- WIDGET) in Pre-Display, become effective after completion of an optional child. Also, some Pre-Display code that had to be duplicated in Post-Invocation no longer has to be.
- To revert to the 4.1 behavior, define an environment variable APPX_41_EPS.
- Appx uses the following sequence of events (after returning from an optional child) in older releases:
- In release 4.2, Appx uses the sequence of events (after returning from an optional child) as follows:
-
- --- KEYMAP NAME is set to "DATA ENTRY" or "MENU ENTRY"
- The SELECT IMAGE (Frame-Level) event point is executed. You can select a different alternate image here, or you can suppress optional images.
- Frame-level widgets are copied from the EM into the --- WIDGET file.
- If the image chosen by the SELECT IMAGE event point should be skipped during live operations and --- OPERATIONAL PHASE is LIVE OPERATIONS, the image is suppressed.
- The characteristics (Editable, Bright, etc.) for all items are set to their default values (based on entry level, security, etc.)
- The default cursor position is computed
- Any MESSAGE's, WARNING's, or ERROR's are displayed
- Data lookups are performed
- Image-level widgets are copied from the EM into the --- WIDGET file
- The PreDisplay/Verify event point is executed
- The PreDisplay event point is executed
- The Global PreDisplay event point is executed
- All items are converted from internal form to external form (i.e. DISPLAY'ed) according to the usual rules.
- The image is displayed to the user
Pre-PCF Update EP executes in auto child - ECR Number 6284
Pre-PCF Update EP now executes in DELETE - ECR Number 5721
- Pre-PCF-Update event points now execute during Delete mode. File level Pre-Update event point now execute for a PCF deletion and for an ILF DELETE statement.
- An ERROR statement executed in either Pre-PCF-Update or in the file level Pre-Update will cancel a Delete operation.
- The ILF DELETE statement now sets the next level of T/F flag, indicating whether the deletion occurred. If an ERROR statement cancelled the deletion, the next level of T/F flag is set to F.
Restore cursor pos after child completes - ECR Number 6854
SCAN now starts at specified value - ECR Number 6098
Scrolling input causes Bad Reg No error - ECR Number 6841
WIDGET attributes changed via ILF now reset - ECR Number 5323
- Each PCF cycle now resets the --- WIDGET records to their default values. Previously, if you updated --- WIDGET file widgets using ILF, the updates remained in effect until the EM was reloaded from disk. The reload only happens when EMs are rebuilt, you exit APPX, or the EM is pushed out of memory and reloaded.
- To deal with this, make sure you always set your widgets. Don't assume a widget has a certain value and set it only on the exception condition. Always set it.
KEATERM
KEA Term hangs on Select Access Path - ECR Number 6861
Language Translation
Build dictionary util now incl widgets
Modified widget text now translates - ECR Number 6427
- The "label" and "tooltip" fields within a widget are "translatable" fields.
- The foreign text appeared in the --- WIDGET file. Designers need to see the base-language version at runtime.
- We now defer widget text translation until after the PreDisplay event point has completed. This change allows the values in the label and tooltip fields to be in the "base" language when manipulated via ILF.
Output Processes
Default print directory relocated
Designer has more control over blank lin
- Designers now have more control over the extra blank lines that have previously been created in "standard" page headings and subheadings.
- Blank line after the separator line has been removed
- Blank line after the generated report heading has been removed
- Blank line after system generated subtotal lines has been removed
- Blank line before a system generated subheading has been removed
- The blank line after a system generated subheading remains
- Designers may need to add blank lines to some process to retain desired spacing.
GUI title bar not displayed in Key Entry
Panning now works for all report sizes - ECR Number 6806
PDF headings for existing reports
Print? check box now displays correctly - ECR Number 5549
Query Processes
Query audit fields updated in INQ mode
Query on key substring fails - ECR Number 6836
SCAN Type 1 does not work - ECR Number 6872
Subroutines
mm_memset() causes random crashes - ECR Number 6776
RT_WRITE_STREAM returned false negative - ECR Number 6568
STREAM OPEN can now open a pipe - ECR Number 6902
- The --- STREAM OPEN subroutine now opens a pipe to a command, if the first character of --- STREAM FILE PATHNAME is a pipe character (i.e. '|').
- Currently we only support one-way pipes. If the STREAM OPEN TYPE is set to 'r', you can read from the child's standard output stream. If the STREAM OPEN TYPE is set to 'w', you can write to the child's standard input stream. (This is consistent with the standard Unix model for the popen() function.)
- The rest of the STREAM API is unchanged. Once you have a successful result from STREAM OPEN, you can use the other STREAM subroutines in the same way that you would use them to interface to a plain file.
- Note: On a Windows host, you must invoke console (rather than GUI) applications whenever you use the pipe feature. (GUI applications don't have a stdin or stdout.)
- On Windows hosts, the popen() function will automatically prepend the name of the command processor if it's not included in the command string. So, if you set STREAM FILE PATHNAME to "|DIR C:*.*", Appx runs the command "%COMSPEC% /C DIR C:*.*" and returns a stream to that command's standard output (in "w" mode), or the command's standard ...
System Administration
Logging
Usage log can now be activated - ECR Number 1830
- Setting environment variable APPX_USAGE_LOG to a filename now produces an Appx Event log. If the filename ends in ".dat", the log is created as a variable-length consecutive file with 1037-byte records.
- You can mask APPX_USAGE_LOG with APPX_USAGE_BITS, setting it to any combination of the following hex values:
00000001 (dec 1) - logs process begin and end (OS process ID, application ID, version, database, process type, and process name) 00000002 (dec 2) - log CASSERT's 00000004 (dec 4) - currently unused 00000008 (dec 8) - currently unused 00000010 (dec 16) - log CANCEL, ERROR, WARNING, and MESSAGE statements 00000020 (dec 32) - log ERROR, WARNING, and MESSAGE statements 00000040 (dec 64) - log WARNING and MESSAGE statements 00000080 (dec 128) - log MESSAGE statements 00000100 (dec 256) - log TRACE messages 80000000 - log date and time of process execution
- For example: APPX_USAGE_BITS=0x00000001 would log only processes begin and end. APPX_USAGE_BITS=0x80000103 would log the process begin and end, the date and time execution started and ended, and and CASSERTs (01 + 02 + 100 = 103).
- These are hex values so 00000040+00000080 is not 00000120, it is 000000c0 (decimal 192).
- The first record written for each session contains the time, OS process ID, and user name.
- If APPX_USAGE_BITS is not set, then APPX_USAGE_LOG logs all of the above events.
- Log file types other than AppxIO are *not* multi-user safe. You should only use .dat files for USAGE logs. When you log to a .dat file, the file will always reside in the 0SA data directory and you should not include a directory (or drive name) in the environment variable.
Other
PDF form type in Disposition
- Form definition in System Administration now supports selection of text or PDF as a form type. This is a new field. Appx assumed a form type of text in prior releases
Security
Query fails if 0SA USER SYS ID reference - ECR Number 6878
- 0SA USER SYS ID had a damaged data-lookup definition that threw off the Query processor, when it was used in a Query.
Application Design
-
0LA Application
-
Data Dictionary
-
Debugging
-
General
-
GUI Application Design
-
ILF Editor
-
ILF Statements
-
Image Editor
-
Input Process Design
-
Menu Process Design
-
New 0-App for Runtime Routines
-
Output Process Design
-
Query Process Design
-
Tech Doc
-
Utilities
0LA (---) Application
New subroutine - CLEAR PASS LIST
New subroutine - DELETE MODE BUTTONS
New subroutine - DELETE SCROLL BUTTONS
Data Dictionary
FLEP can now be compiled within design
Phantom DL indicator fixed
Debugging
Restore cursor pos after ILF debugger - ECR Number 6853
General
Default mode in application design changed
GUI Application Design
All design utilities are now GUI - ECR Number 6834
Named Resources available across applications
Override OPTION for optional children
ILF Editor
Additional help documentation
Auto-change appl ID to --- when approp. - ECR Number 6104
- When editing ILF code, Appx now changes the application ID to "---", if the referenced field (or file or process) cannot be found in the application specified by the designer, but does exist in application 0LA.
- This lets you refer to pre-defined fields, files, or processes without having to change the application ID.
- If you code an I/O statement (such as READ, WRITE, READNEXT, etc.) and the name of the file you want to manipulate is the same as the name of a work field, the ILF editor will not complain with a "File Not Found" error message.
Completion of ILF editor field names
SET TAR CUSTOMER Nand you press F5 (Next Record), the ILF editor will change it to:
SET TAR CUSTOMER NAMEpress F5 again and it becomes:
SET TAR CUSTOMER NUMBER
Cursor position corrected after Help - ECR Number 5834
Errors now cause beep
File name now validated for RESTORE stmt - ECR Number 6115
ILF Editor crash fixed - ECR Number 6882
Invalid fields allowed in ILF statements
New Cut, Copy, & Paste capabilities - ECR Number 6747
- The ILF editor now has an ILF clipboard. Any time you do a copy or a move, ILF is saved in the clipboard, allowing it to be pasted multiple times.
- Two new ILF editor options allow you to SELECT a range of ILF statements and COPY them into the clipboard.
- If running the Java Client, the ILF clipboard uses your desktop clipboard. If not running the Java Client or if the application is locked, the ILF clipboard uses an internal clipboard rather than the desktop clipboard. The desktop clipboard allows statements to be pasted into any desktop application.
SCAN ability enhanced in ILF Editor
SCAN in ILF on field and file names
SCAN on ILF commands lists all commands - ECR Number 5318
Statement validation has been improved - ECR Number 6849
XCOPY now works for locked applications - ECR Number 4630
ILF Statements
--- STREAM i/o routines enhanced
CNV PORT - New Statement
CNV TEXT - T/F result flag corrected - ECR Number 6535
IF DIFF - New Statement - ECR Number 6506
----- IF DIFF --- ---------------------- --- -------- (1) (2) (3) (4) (5) 1 - T/F flags 2 - Application ID 3 - Field or Record Name 4 - Occurrence Number 5 - Comparison Type (STORE, DEFAULT, or ORIGINAL)
- The comparison type can be STORE, DEFAULT, or ORIGINAL. IF DIFF will compare the current value of the operand against the STORE/RESTORE area (STORE), the default record (DEFAULT), or the original (on-disk) buffer (ORIGINAL). ORIGINAL is only valid for the PCF (because we don't store the original on-disk values for other files).
- If no differences are detected, IF DIFF will set the next T/F flag to F. If differences are detected, IF DIFF will set the next T/F flag to T.
- IF DIFF will also populate the --- COMPARE memory file with a list of differences. If no differences are found, --- COMPARE will be empty. If differences are found, --- COMPARE will hold one record for each changed field. The --- COMPARE record is composed of the following fields:
COMPARE FIELD NAME X(22) (Primary key) COMPARE DESCRIPTION X(30) COMPARE CURRENT VALUE X(80) COMPARE OTHER VALUE X(80) COMPARE OFFSET 9(5) COMPARE LENGTH 9(5)
- COMPARE FIELD NAME will contain the name of the changed field.
- COMPARE DESCRIPTION will contain the descriptive name of the changed field.
- COMPARE CURRENT VALUE will contain the value of the field in the current record buffer, as converted by CNV TEXT.
- COMPARE OTHER VALUE will contain the value of the field in the other record buffer (store, default, or original) as converted by CNV TEXT.
- COMPARE OFFSET and COMPARE LENGTH fields will contain the offset of the field within the record buffer and the length of the field, respectively.
- To make it easier to use IF DIFF in a subroutine, you can omit the operand name if the comparison type is ORIGINAL (since that implies the PCF record).
- There were a few questions and suggestions about the first proposal. Here are a few changes:
-
- Any process that has a PCF can compare to the original-record buffer.
- Since file-level event points have a PCF, they can compare to the original-record buffer.
- The original-record buffer is now shared between the file-level event points and the foreground process. This change was necessary to fix a bug in the current implementation of file-level event points. Prior to this change, you could modify a record in the file-level Post Read event point and the foreground input process would not notice that the record had changed.
-
Here is a short description of how the original-record buffer is managed:
- In Add mode, the default-record buffer is copied to the original-record buffer just before the Set Default Values event point
- In Inquire, Delete, or Change mode, the original-record buffer is copied from disk just before the Post PCF Read event point
- For file-level event points, the original-record buffer is copied from disk just before the Post PCF Read event point
- In Change mode, the current-record is copied to the original-record buffer just before the Post PCF Update event point
- In Add mode, the current-record is copied to the original-record buffer just before the Post PCF Update event point
- For process types other than Input, Appx never updates the PCF automatically, so rules d and e only apply to Input processes
- For file-level event points, each stream maintains its own original-record buffer
- For release 4.2, we will only keep an original-record buffer for PCF files - we may change this restriction in a future release.
- You can scan for the comparison type in the ILF editor
LOCAL - New Statement - ECR Number 6105
- A new LOCAL statement allows fields to be declared to be LOCAL to the current context.
- LOCAL saves the named field's value. When the current context completes, it restores the saved value before returning to the invoking context.
- LOCAL works in subroutines called via a GOSUB, and in Start of Process event points.
RESTORE - New option: ORIGINAL
Image Editor
GUI Windows properties accessible from Image Editor toolbar and pull-down
WIDGET cut, copy, paste loses micro adj - ECR Number 6846
Input Process Design
Add, Delete, Change widgets at runtime - ECR Number 5442
Display Only flag unexpectedly changes - ECR Number 6871
Generate Column Headings
New --- PDF – CURSOR AT FIELD
Toolbar now defined in hookable process - ECR Number 6246
- The standard toolbar buttons that APPX automatically includes can now be customized. They are defined in an input process called STANDARD TOOLBARS.
- This process can be design transferred into your application from the 0LC application, modified, then hooked to run your customized STANDARD TOOLBARS process.
Widget state is now context sensitive - ECR Number 6252
- Appx now disables certain widgets depending on the current context (current phase, entry level, etc.).
- For example, a button which sends the ACKNOWLEDGE DELETE option should be disabled unless you are in Delete mode. A WIDGET ENABLED flag can hold Yes, No, or blank. If the designer leaves the Enabled flag set to blank for a widget, the engine should control the enabled/disabled state as appropriate. If the designer sets the WIDGET ENABLED flag to Yes or No, the engine should not modify the enabled/disabled state.
- If Delete Mode is not allowed in the current process, Appx disables widgets that sends the --- DELETE MODE option. After the PreDisplay and PreDisplay/Verify event points, Appx examines any --- WIDGET records where --- WIDGET ENABLED is set to ' ' (blank). For such widgets, Appx disables (i.e. set --- WIDGET ENABLED to 'N') if the related option is invalid in the current context.
- To let Appx manage widgets' enabled/disabled state, set --- WIDGET ENABLED to blank. To retain explicit control over the enabled/disabled state, set --- WIDGET ENABLED to 'Y' or 'N'.
- All toolbar buttons, even those generated by Appx (End, Cancel, Next Record, etc.) appear in the --- WIDGET file, so designers can control toolbar buttons as well as their own.
-
Appx follows these rules when deciding whether to disable a widget:
- CANCEL ....... If --- CANCEL OK is 'N' or Cancel Disposition is 'Prohibit', disable the widget.
- WIDGET OPTION >= USER 0 and WIDGET OPTION <= USER 255 ....... If there is an optional child and the child entry level prohibits the child from running, disable the widget
- ACKNOWLEDGE DELETE ....... If --- INTERACTIVE PHASE is not 'DATA DELETION", disable the widget.
- DIRECT PROCESS 1 ....... If you don't have a Direct Process 1, disable the widget.
- DIRECT PROCESS 2 ....... If you don't have a Direct Process 2, disable the widget.
- SET ITEM ATTRIBUTES ....... If there are no items on the current image, disable the widget.
- ADD MODE ....... If the mode is not allowed (or not in an input process), disable the widget.
- DELETE MODE ....... If the mode is not allowed (or not in an input process), disable the widget.
- INQUIRE MODE ....... If the mode is not allowed (or not in an input process), disable the widget.
- CHANGE MODE ....... If the mode is not allowed (or not in an input process), disable the widget.
- SCROLL FIRST ....... If not in a scrolling process (or you're at the first record), disable the widget.
- SCROLL PREVIOUS ....... If not in a scrolling process (or you're at the first record), disable the widget.
- SCROLL DOWN ....... If not in a scrolling process (or you're at the first record), disable the widget.
- PAN TOP ....... If you can't PAN UP, disable the widget.
- PAN UP 1 ....... If you can't PAN UP, disable the widget.
- PAN UP SCREEN ....... If you can't PAN UP, disable the widget.
- PAN BOTTOM ....... If you can't PAN DOWN, disable the widget.
- PAN DOWN 1 ....... If you can't PAN DOWN, disable the widget.
- PAN DOWN SCREEN ....... If you can't PAN DOWN, disable the widget.
- PAN LEFT MARGIN ....... If you can't PAN LEFT, disable the widget.
- PAN LEFT 1 ....... If you can't PAN LEFT, disable the widget.
- PAN LEFT SCREEN ....... If you can't PAN LEFT, disable the widget.
- PAN RIGHT MARGIN ....... If you can't PAN RIGHT, disable the widget.
- PAN RIGHT 1 ....... If you can't PAN RIGHT, disable the widget.
- PAN RIGHT SCREEN ....... If you can't PAN RIGHT, disable the widget.
Widgets erroneously deleted - ECR Number 6759
Menu Process Design
Menu image editor mode problem fixed
New 0-App for runtime routines
0LA Runtime processes can now be copied - ECR Number 6778
- A new application, 0LC, is now installed with Appx. This application contains some of the processes we provide in 0LA. We want to provide for designers to be able to customize the look and feel of these processes. The process can design transfered to the desired application to be used by designers as the starting point for their own processes. The original processes in 0LA could then be overridden by a HOOK record.
- The 0LC application is read-only. Processes may be transferred out but may not be modified within the 0LC application.
Output Process Design
GUI Output can now be designed - ECR Number 6819
GUI Output can now be printed (PDF) - ECR Number 6819
Opt 6 on Output Image Editor fixed
Query Process Design
Wrong event points loaded for editing
Tech Doc
Can now be printed within Process Design
Printed Tech Doc for widgets & Resources - ECR Number 6431
Utilities
Added new Design Compare Utility - ECR Number 6449
Added new Export/Import util for Design - ECR Number 6450
Change All References will process data - ECR Number 6318
Gen rpt: Date fields no longer autototal - ECR Number 5646
New utility to locate misplaced widgets
Xcopy and Design Transfer on locked appl - ECR Number 4630
Database Management
Recover Utility
Recover fails on files larger than 2GB - ECR Number 6890
- The Recover utility no longer fails on files greater than 2 Gigabytes. The Recover utility has been incorporated into the Appx engine on all platforms. It can be invoked by executing appx -recover. The format of the command is the same, appx -recover old_filename new_filename deleted_filename.
Restructure Utility
Can't restructure 2,000 byte records - ECR Number 6749
- Prior to 4.2, restructuring a file containing records with an original length an even multiple of 1000 bytes, would fail with an "Invalid Prototype Record Length" error.
Failed restructure causes other problems - ECR Number 4570
- When Restructures failed for some reason, subsequent Restructures could fail with errors like "Element file write - error already on file". Failed Restructures now cleanup after themselves more thoroughly.
FMS Interfaces
Oracle
Oracle 9i is now supported
- APPX 4.2.0 has been successfully tested with Oracle 9i (9.2.0).
- The APPX 4.2 engine (appx.oracle) has been dynamically linked with the Oracle 9i client software. The Oracle 9i client library (libclntsh.so.9.0) must be installed and accessible on the APPX server.
C-ISAM/DISAM
DISAM96 Version 6.12 is now supported
- The APPX C-ISAM interface has been replaced with a new D-ISAM interface. D-ISAM should be fully compatible with existing C-ISAM files.
My SQL
Various issues - ECR Number 6898
- Various issues relating to storing APPX data in a MySQL data source have been corrected.
- The MySQL ODBC driver, called MyODBC, comes in two versions. You must use MyODNC 3.51 or later. Earlier verison had serious bugs.
- The MyODBC driver erroneously reports some non-numeric data tyeps as being "unsigned" - Appx won't use unsigned data types when it creates a tablein an ODBC database. We have fixed this so that Appx ignores the signedness of non-numeric types.
- MySQL supports the following temporal data types: TIMESTAMP, DATE, TIME, DATETIME, and YEAR. The DATE type will hold CC through DD (century through day). The TIME type will hold hh through ss (hours through seconds). The DATATIME type will holdCC through ss (century through seconds). The YEAR type will hold YY values.
- TIMESTAMP colums can hold a variety of date component ranges: TIMSTAMP and TIMSTAMP(14) columns can hold CC-th (century through hundredths of a second). TIMSTAMP(12) will hold YY-ss, but appears to hold CC-ss because the MyODBC driver will synthesize the century component. TIMESTAMP(8) will hold CC.
Other
Error reporting in RDBMS improved
- We've improved the handling of error messages in our database interfaces (Oracle, ODBC, DB2) so that, if something goes wrong, you should see a meaningful message.
Native FMS interfaces consolidated
- With release 4.2, we're consolidating some of our FMS interfaces. We will be dropping direct support for Sybase and Vision, but we will continue to support those databases through ODBC (you'll need to acquire an appropriate ODBC driver). The old interfaces for Sybase and Vision will still be available for a while but are no longer "officially" supported.
APPX GUI Client
APPX Client Login Dialog Window
New startup sequence
Options tab - "Advanced" button added - ECR Number 6817
- An "Advanced" button has been added to the "Options" tab of the APPX Client login dialog window. Clicking on the "Advanced" button opens a "Client Properties" window with a list of properties and values. The properties list includes all of the options that were previously available as command line options as well as the options that were available on the client Options pulldown menu at runtime. A few new options have also been added.
- The values of the various properties can be edited and are saved when the properties window is closed. These properties are then used when the client window is opened to connect to a host.
Options tab - New "GUI Looks" available
- The Options tab of the APPX Client Login dialog now has six options to choose from when setting the GUI Look. The available GUI Look choices are:
- Note that some GUI Looks are not available on all client platforms.
Client Preferences/Command Line Options
Command line overrides saved properties
- You can now override all "saved" Client Properties by specifying the property and the desired property value on the client startup command line.
- The syntax of a property on the command line is as follows:
- For example:
- Properties specified on the command line override the corresponding saved properties but do not change the saved properties.
New Client Properties Window
- A new Client Properties window allows easy viewing and editing of a wide variety of saved client preferences.
- The Properties editor can be accessed by clicking on the Advanced button on the Option tab of the client login dialog or the Properties Editor can be accessed by selecting "Preferences" on the "File" pulldown menu during a client session. Note that some properties are not editable when access during a client session.
User Client Preferences Now Saved
- Client options that are enabled or disabled via the "Options" pulldown menu at runtime are now remembered (saved) between client sessions.
- The user "preferences" for these options are separately saved for each user of a desktop computer in a "preferences.ini" file in the ".appx" directory in the user's home directory. So, if two users share a desktop computer, they will each have their own saved Client preferences provided that each user logs in with a unique desktop login id.
- These same options appear on the new Client Properties list where they may also be enabled or disabled. The values listed on the properties list represent the currently saved option values. The values shown in the properties list are used to enable or disable the various options when the client is initially started.
Runtime Environment
Desktop Client now uses Sun Java 1.4 VM
Reportwriter (SQL)
Report Design
Appx Report Writer revamped
- All reported bugs in the Appx Report Writer have been fixed as of release 4.2
Microsoft, Windows, Windows Server, Windows 2000, Windows Server 2000, Windows Server 2003, Windows 98, Windows NT 4, Internet Explorer, Windows Vista, Windows XP, Windows 7, Microsoft SQL Server, Microsoft Access and Microsoft Excel are registered trademarks of Microsoft Corporation. All other products may be trademarks or registered trademarks of their respective companies.
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding APPX Wiki? Send feedback