(Linux) #940
Using LOCKED() in rclerk/rreport on Linux could crash filePro.
(All) #941
fPSQL could crash if the query required 10K of output per record. (Default increased to 100K, and it now properly reports error if exceeded.)
(All)
Corrected some licensing issues with session and feature counts not being released in some circumstances.
(ODBC) #943
Define files fails on an ODBC data source when the table name has embedded spaces.
(All) #947
If you have a dummy field which has not been given a length/type in processing, and place it on a screen, and then have a popup screen over that field, and when the popup isn't active (ie: after a POPUP UPDATE, but before a CLEARP, do a SHOW "@...", the contents of that dummy field will bleed through to the popup.
(All) #951
If you have a fuzzy browse lookup with "show=pkeep", filePro would crash upon re-executing the lookup.
(All) #952
New system array -- @FUZZY[] -- contains information about the most recent fuzzy browse lookup.
Currently, the only info available is the record number, via @FUZZY.RECNO[subscript]
(All) #954
If you have any pending PUSHKEYed keystrokes, the filePro processing debugger didn't update the screen as you stepped through processing.
(All) #955
-SX flag to *report did not load the selection set.
(All) #956 Memo editor spellcheck crashes
Pressing F8/S in the memo editor to run spellcheck would crash filePro if you hadn't previously done a SPELLCHECK() function within processing.
(*nix)
On Unix/Linux, when not using the license server, if the license file was missing or was determined to be invalid for any reason, the filepro program would abort with a segmentation violation. This has been corrected and the filePro program now displays a licensing error message and exits cleanly.
(*nix)
On Unix/Linux, when not using the license server, filePro could incorrectly create many semaphores and shared memory segments.