<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="x-western"><font face="Arial">A new
filePro revision 5.6.08 is now available on
our website.<br>
<br>
See the readme for a list of bug fixes.<br>
<br>
Thank you<br>
<br>
fP Sales<br>
<br>
</font><font face="Arial">(Windows) #1016<br>
ddefine did not allow filenames with "." in Windows<br>
<br>
(Linux) #1018<br>
showlock did not display all locked records Linux<br>
<br>
(All) #1026<br>
Only one index was deleted when selecting multiple indexes in
ddir/dprodir<br>
<br>
(All) #1072 - enhancement<br>
GETENV("PFREADONLY") will now return "ON" if the "-ro" flag is
used, even<br>
if not set in the environment.<br>
<br>
(Quickstart) #1075<br>
If you have a label "foo" and another "foo-bar" (ie: the same
prefix, with<br>
a hyphen and a suffix added), references to "foo-bar" would refer
to "foo"<br>
if "foo" occurs earler in the processing.<br>
<br>
(All) #1068<br>
If you had something following the "b=(expression)" part of a browse<br>
lookup which "looks" like part of a valid expression, filePro would<br>
take that as part of the "b=(expression)" part of the browse lookup.<br>
<br>
For example:<br>
<br>
lookup foo k=xx i=a -nx b=(brwhead&brwdata) *2"<br>
<br>
(If, for example, you were to edit the lookup line to remove a
literal<br>
browse lookup, and missed the trailing "*2".)<br>
<br>
(All) #1021<br>
In dcabe, if you load a processing table with a DECLARE GLOBAL and
syntax<br>
check it, and then load and syntax check another processing table
which has<br>
the same DECLARE GLOBAL name, but a different definition, you would
get an<br>
"already defined" warning.<br>
<br>
(All) #1040<br>
EXIT in @ONCE processing didn't exit *report.<br>
<br>
(Linux) #974<br>
Website didn't allow license to be downloaded when using Domain Name<br>
as the license check value for Linux systems.<br>
<br>
(All) #975<br>
The following flags have been added to swapcpu:<br>
<br>
-Q = Quiet mode. Suppresses "file already in destination order".<br>
-CN = Convert to native byte order.<br>
-CF = Convert to foreign byte order.<br>
<br>
(All) #977<br>
swapcpu didn't swap the "blob" file.<br>
<br>
(All) #982<br>
PFMBTO only caused the first message box to time out. All
subsequent<br>
message boxes still required Enter.<br>
<br>
(Windows) #1016<br>
On Windows, ddefine did not allow you to create or access files with<br>
a dot in the filename.<br>
<br>
(All) #1040<br>
EXIT in @ONCE processing in *report did not exit.<br>
<br>
(Linux) #1071<br>
On some systems, a fresh filePro install would fail with "fatal
error<br>
check current user count: invalid argument".<br>
<br>
(All) #1077<br>
filePro 5.6 is now available on FreeBSD.<br>
<br>
(All) #1088<br>
Calling READLINE() with an uncast dummy field, which has never been<br>
assigned a value, and not including a maximum length, could crash<br>
filePro.<br>
<br>
(All) #1099<br>
There was a memory leak in nested CALLs which has been fixed.<br>
<br>
(All) #1100<br>
Under some circumstances, filePro would not use the available free<br>
space in the blob file for new blobs/memos, causing the blob file to<br>
grow larger than needed.<br>
<br>
Note that the updated blobfix utility can be used to "fix" this, and<br>
shrink the blob file to the "correct" size.<br>
<br>
(All) #1101<br>
If you have a lookup to a file that has an automatic index built on<br>
an associated field group, but the lookup is not on that index, it<br>
was possible for filePro to crash.<br>
<br>
(All) #1102<br>
Executing a LOOKUP in a processing table, CALLing another table<br>
which executes a LOOKUP to the same file, and then CLOSEs that<br>
lookup, can cause filePro to crash and/or give unusual errors<br>
upon re-executing the LOOKUP in the original processing table.<br>
<br>
(Linux) #1103<br>
The Linux distribution included an old "lib/rename" utility, which<br>
wouldn't run on some current Linux distributions.<br>
<br>
(*nix) #1014<br>
User-count debug logging can now be controlled via the new config<br>
variable "PFCHKUSER=logfilename".<br>
<br>
(All)<br>
xfer now handles the blob file.<br>
<br>
(*nix)<br>
filePro could crash in some debugging modes of the system
environment<br>
variable MALLOC_CHECKS.<br>
<br>
(*nix) #1070/#1096/#1097/#1098<br>
Some places in filePro didn't properly require double-break.<br>
<br>
(*nix)<br>
Debug versions hard-coded the user-count logging filename. This is<br>
now controlled with PFCHKUSER=logfilename.<br>
<br>
(All)<br>
OPENDIR() could crash if given a directory with thousands of files,<br>
all in alphabetical order.<br>
<br>
(All)<br>
If a user menu's title and version number filled the space allotted,<br>
filePro could crash.<br>
<br>
(*nix)<br>
On some *nix systems, DEL (when not used as the Break key) would not<br>
be treated as a backspace.<br>
</font><br>
<pre class="moz-signature" cols="72">--
fP Sales
<a class="moz-txt-link-abbreviated" href="mailto:sales@fptech.com">sales@fptech.com</a>
800-847-4740
</pre>
</div>
</body>
</html>