Release notes - filePro Plus 5.6 fP 5.6.06 The filePro Plus software and the documentation provided with it are protected under United States Copyright Laws and is provided subject to the terms and conditions of the filePro License Agreement. PLEASE NOTE : the support and fax phone numbers listed in this readme file are new. They have changed since the last release. ******************************************************************** WWW http://www.fptech.com Support fpsupport@fptech.com Sales sales@fptech.com Management filepro@fptech.com ******************************* To submit bug reports -------------------------------- 1. FAX them to (607) 655-5654 clearly marking them as bug reports 2. EMail them to fpsupport@fptech.com including the text "Bug Report" with the version # in the subject line 3. Call the customer support number (800) 847-4740 ******************************* We wish to thank Jim Asman for sending us an entire set of HP printer tables for inclusion in this release. You might wish to send him a note of appreciation to root@spctra.wimsey.com Please view Jim's readme file which has been placed in your fp\lib directory for any special notes about these printer tables. ******************************* Contact Information Surface Mail fP Technologies, Inc. PO Box 290352 Tampa, FL 33617-0352 Phones Support (800) 847-4740 Sales (800) 847-4740 Fax (607) 655-5654 Email Support fpsupport@fptech.com Sales sales@fptech.com Management filepro@fptech.com Bug Reports Email - fpsupport@fptech.com including the text "Bug Report" and Version # in the subject line FAX - (607) 655-5654 marked as Bug Report and Version # Phone - (800) 847-4740 It's important that you clearly describe a suspected bug and include the filePro version number. If the programmer has trouble figuring out what you meant, you might as well not have reported the bug. Be very specific. For example, if you are reporting a bug concerning a Browse, identify if it is a lookup browse or browse created by using the [F6] key. A screen shot is very helpful and sometimes better than more than 1000 words. Describe exactly how to duplicate the bug. Although it's sometimes difficult to create a working sample to demonstrate the problem, make every effort to trim down your code and provide a working sample application with test data. You may even discover that what you thought to be a bug is due to a coding error or the bug may only occur with lots of data or large processing tables. Take good notes as to any error messages and under what circumstances the error message is presented. It never hurts to provide more information rather than not enough. This is particularly true when the programmer asks for additional information. Rather than responding with a single sentence, be verbose since this may shed some light on the bug or what you may be doing wrong in your code. Read what you wrote. Closely read your bug report before submitting to make sure it's clear and complete. If you have listed steps for duplicating the bug in a sample, exercise the sample with the listed steps to make sure you haven't missed a step. ========================= 5.6.06 Release Notes ========================= (Nix) #968 When running without the license manager, *report and *cabe did not release their session license upon exit. (Nix) #965 The SCO version of filePro could fail to validate a MAC-address-based license if enough filePro sessions were open. (Even though there were less sessions than the license would allow.) (All) #966 If you have a lookup file with memo fields, and do a COPY to that lookup, the memos won't be copied correctly. (All) #963 If the cursor is on the last line of a wordwrapped line of text, and is on the first line within the memo editor window, and the rest of the window is filled with additional text, then placing the cursor at the end of the text on that line and backspacing such that the now-shorter text would re-wordwrap to take less lines, taking the cursor to the text which has been re-wrapped to the previous line (ie: the one above the top of the window), can cause filePro to crash. (All) #967 In the memo editor, using the up and down arrows, if the cursor is in a column on the source line beyond the last column of the destination row, the cursor may be placed in the wrong location. ========================= 5.6.05 Release Notes ========================= (All) #949 The 2-digit-year system date fields resolved without an EOF marker in dscreen/dmoedef. (All) #957 LISTBOX() would expand embedded TAB characters within items. (All) #958 If you are on the last line of text in a memo, and that line wraps, and the end of that line (ie: the end of the memo itself) is visible as the last line in the memo window, and you start deleting text on that line such that the wordwrap now takes up less lines (ie: the word on the last line gets "pulled" up to the previous line), then filePro can crash. (All) #959 autoshuf didn't run with a runtime-only license. (All) #960 The default value for PFLISTSLASH has been changed from ON to OFF. (*nix) #961 Under certain circumstances, the first time you accessed a licensed feature, filePro would freeze while doing the license check. This only happened if the license manager was not running. ========================= 5.6.04 Release Notes ========================= (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. ========================= 5.6.03 Release Notes ========================= (*nix) fplmserver wouldn't recover disconnected sockets in a timely manner. (SCO OSR5) fplmserver would freeze when running a filePro program from within a SYSTEM command on SCO OpenServer 5. (All) #939 PFNUMIXBUILD was incorrectly documented as allowing up to 128000. The real maximum is 32767, which is now enforced by filePro. (Setting it higher than the maximum value will result in using the maximum.) (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. ========================= 5.6.02 Release Notes ========================= (All) #939 PFNUMIXBUILD was incorrectly documented as allowing up to 128000. The real maximum is 32767, which is now enforced by filePro. (Setting it higher than 32767 in previous versions could crash filePro.) (*nix) Some license server sockets in fplmserver were not being closed and released in a timely fashion. (OSR5) Nested sessions of clerk/report could cause an infinite loop in the license server on OpenServer 5. (*nix) Problems with the DEL/Ctrl-C interrupt on multi-threaded platforms could cause crashes. (Linux) filePro had problems with the shared libtermcap on 64-bit Linux platforms, so we now statically link to our own termcap library. (All) @LICENSE[] will now show a feature as licensed, even if the session limit has been reached for that feature. (All) #924 PFNODFMSG=OFF turns off ddefine's "PFNODF=ON" notice. (Default: ON) (*nix) #925 Fixed a problem on *nix boxes with filePro not properly counting sessions if the license manager is not running, and one filePro program calls another. (5.6) #928 RECV() and RECVLINE() now accept DECLAREd variables, in addition to real and dummy fields, as the destination. (Windows) pmaint now has an F6 option to display a list of system-defined printers while in the "destination" field of the printer config screen. (All) #927 Fixed a problem with node_addr and DKNF errors on indexes which are larger than 65536 blocks in size. (5.6) #937 Added PFENTSELDISABLE=list to disable (and remove prompts for) a set of default behavior of *clerk at the "Enter Selection" prompt. A question mark ('?') represents HELP. Note that the HELP key cannot be disabled with this variable, although you can keep the new prompt from appearing. The default value is "?", which causes the same prompts as before to appear. Any "invalid" keys listed are ignored. Note that any @KEY events are not disabled. Only filePro's default behavior for the keystrokes is affected. Also note that, if the HELP key label is longer than 3 characters, enabling all of the prompts will not fit in 80 columns. (All) #938 MEMO handle EXPORT filename APPEND BLOB handle EXPORT filename APPEND Would crash at runtime. (All) #931 FIELDNAME/LEN/EDIT/VAL didn't take an expression for the field number. (ODBC) #932 dreport was unable to post new records to some high-level ODBC data sources. (*nix) #933 If you were to have a variable/array/lookup/etc called "USER", then the parser would allow some invalid syntax, where part of an expression was missing, such as "aa = bb +". (Linux) #934 There are two distinct, and incompatible, pty methods on different Linux boxes. fpdaemon now includes both methods in a single binary, and determines at runtime which method to use. (All) #935 dxmaint would show "not available" on indexes that were in use, but it would still let you rebuild them. (All) #936 MEMO...SHOW now accepts the NOWRAP flag, just as MEMO...EDIT does. (Linux) #926 fpcopy would fail with "cannot create new data file" on some Linux systems. (*nix) #929 DOKEY would not work if you used a lower-case letter. ========================= 5.6.01 Release Notes ========================= (*nix) Problems with the DEL/Ctrl-C interrupt on multi-threaded platforms could cause crashes. (Linux) filePro had problems with the shared libtermcap on 64-bit Linux platforms, so we now statically link to our own termcap library. (All) @LICENSE[] will now show a feature as licensed, even if the session limit has been reached for that feature. =================================== 5.0.15 Release Notes and 5.6 fixes since 5.0.14 =========================== See 5_0_15_readme.txt for fixes since 5.0.14 =================================== Spooling for Native Windows filePro =================================== Windows apparently doesn't spool print jobs sent by native windows console applications to local printer ports, the way that it does for MS-DOS programs that do the same thing. (That is, open "lpt1" as a file and write to it.) We have added the necessary code to the native windows version of filePro to use the Windows printer routines (ie: OpenPrinter, StartDocPrinter, etc.) which do respect the Windows spooler. However, the spooler is also limited to those printers defined in the printer control panel. Therefore, we have made it a requirement that, in order to use the Windows spooler, you must prefix the filePro destination with "win:", as in "win:lpt1:". The rest of the destination must be the exact port name or printer name as you have defined it to Windows. So, if you have a printer attached to LPT1 that is named "HP DeskJet 870Cse", you would use either: win:lpt1: or win:HP DeskJet 870Cse If you have a network printer "\\server\printer" that is captured to LPT2, called "Bob's printer", and the Windows destination is "\\server\printer" then you would use either: win:\\server\printer or win:Bob's printer You could not use "win:lpt2:" as "lpt2" is not the destination that Windows knows the printer by. (Though you could use "lpt2" without the "win:" and go directly to that port without the spooler.) Remember: You can only use the exact port name or printer name that Windows uses. Anything else will result in a "the parameter is incorrect" error when filePro tries to open the printer. ******************************* ******************************* filePro and filePro Plus are registered trademarks of fP Technologies, Inc. ******************************* =================================== End End End End End End End End End ===================================