APPX Server 4.0.1 Release Notes


  • APPX will now only attempt to lookup and display user IDs for record locks if the track locks FMS control is set for the file. (#4604)
  • 4.0.0 for Windows® required three DLLs (MFC42D.DLL, MSVCRTD.DLL, MFCO42D.DLL) in order to run APPXODBC/ASQL. These are no longer required. (#4676)
  • You can now specify a username and password when defining an AppxNET FMS path. The format of the FMS path name for AppxNET has been modified to: username:password@host:port Valid variations are: username:password@host:port host:port (#4681)
  • If a SCAN was pressed when not in KEY ENTRY mode, it could display a blank screen. If the user exited and pressed SCAN again, it could hang the session and consume large amounts of CPU time, until killed. (#4689)
  • If the enduser SCANned a key segment which had a Data Lookup defined, and that key segment would not ordinarily be editable (but is editable because of being in key entry), the SCAN processor would display a "zero bytes requested" message. (#4692)
  • The byte-order translation logic in AppxNET was incorrect if you were hosting a file on an Intel server and trying to access that file from a RISC client. (#4693)
  • In release 4.0, if multiple dispositions were run in a job, or if a disposition was re-run, it could incorrectly retain a defaulted value and yield the error "Disposition Definition Not Found". Another symptom of this problem was a disposition using a definition record from a previous disposition and not selecting the appropriate one. (#4699)
  • On character mode terminals, keystrokes recorded as a macro are now preserved between APPX sessions. They are retained in the file ".appx mac" in the current directory (the user's current directory when APPX was launched). This feature was added in APPX 4.0 but was not included in the release notes. (#4716)


  • Converted Speed II applications could have fields in the data dictionary that have user documentation, but the documentation would not show at runtime if HELP was pressed.
  • This fix is to the Synchronize Design Elements process. In order for it to take effect, you need to run this process for each application. This can be found in Utilities | Toolbox | Conversion Utilities. (#2338)
  • Under Windows Presentation Client's APPX SCRIPT OUT, process names are now recorded.
  • This means that a SCRIPT OUT logfile may be copied mid-way through a Windows session, in order to capture what a user does only up to a certain point in an APPX session. It also means that if the APPX session bombs out part way through, the SCRIPT OUT keystroke/process log is not lost. (Remember that the next time you initiate an APPX session, that the prior SCRIPT OUT logfile is initialized.) (#4650)


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.