Welcome, Guest. Please login or register.

Login with username, password and session length
Pages: [1]   Go Down
Print
Author Topic: 5.6.08, 09 & 10 Readme Notes  (Read 2480 times)
0 Members and 1 Guest are viewing this topic.
Bill Randall
Administrator

Posts: 53


View Profile WWW
« on: December 20, 2009, 07:49:23 AM »

Release notes - filePro Plus 5.6
fP 5.6.10  - 12/08/2009

 
=========================
5.6.10 Release Notes
=========================

(Nix)
    Fixed a bug introduced where @sk did not hold special key when
    exiting a browse.

=========================
5.6.09 Release Notes
=========================

(All)
    The SYSTEM() function would give a syntax error on some platforms.

(All) #1063
    blobfix now takes command line parameters:

        blobfix [filename | -] ( -m qualifier )

(Windows) #1074
    fpcopy would give a "cannot create new file" error upon doing a "copy
    file formats only".

(Quickstart only) #1104
    Executing a LOOKUP in a processing table, CALLing another table
    which executes a LOOKUP to the same file, and then CLOSEs that
    lookup, can cause filePro to crash and/or give unusual errors
    upon re-executing the LOOKUP in the original processing table.

(All) #1105
    The configuration editor did not allow an equals sign to appear in
    the value of a setting.

(All) #1106
    Under certain circumstances, CLOSEDIR() could cause filePro to hang
    or crash.

(All) #1108
    A new config variable, PFPRTFIND=logfilename, was added to help
    debug problems in resolving printer name to destination.

(All) #1109
    In request output, if you execute a CALL in sort/select processing,
    and then execute a CLOSE in output processing with no intervening
    CALLs, filePro would crash.

(All) #?Huh
    The SYSTEM() function would give a syntax error on some platforms.

(All) #596
    blobfix did not properly fix qualified blob files.

(fPSQL) #701
    fPSQL queries that selected based on associated fields behaved
    differently if an index was built on that associated field group.

(All) #865
    Selection sets did not properly compare memo fields no empty.
    For example, if field 6 is a memo field:

        6  ne   <nothing>

    all recods would be selected, even those where field 6 is empty.

(All) #1078
    fpconfig did not allow values which contained an equals sign ('=').

(SCO OSR5) #1031
    fpcopy on SCO OSR5 did not copy files whose name was longer than
    14 characters.

(fPSQL) #1060
    fPSQL on some systems would crash on queries using associated fields.

(All) #1067
    dxmaint did not override PFQUAL of passed -m "" on the command line.

(All) #1094
    A printer with a destination of "LOCAL" was not recognized as
    setting the destination to the local printer.

(fPSQL) #1111
    fPSQL could not use "filename.fieldname" format if the filename
    started with a digit.

    Note that, with this change, invalid numeric literals such as
    "123b4" will now give an "unknown field" error rather than an
    "invalid numeric literal" error.

(All) #1112
    When converting from a non-time field to an HMS field, the conversion
    would not be correct if the input field were longer than 8 characters,
    or the hours value was larger than 99, regardless of the length of
    the destination field.

(SCO OSR5)
    Add a new variable, PFRENEWTIMEOUT=nnn, to control the license renew
    message timeout on SCO OSR5.  The value "nnn" is the number of seconds
    between renewal messages, and can be any number from 2 to 600.  The
    default is 60.

    Note that this variable is unnecessary, and ignored, on other platforms.

    Connectivity issues on OSR5 (cabling, router, TCP/IP stack, network
    congestion) can cause unexpected delays in OSR5 filePro programs (some
    long enough to seem like program hangs). Reducing the value of the
    license renew timeout messages can reduce and even eliminate these
    delays.

(*nix)
    The following environment variables will be set within filePro if the
    license server is not being used:

    PFPID - the process id of the filePro program.

    PFSID - the session id of the filePro program.

    PFLICENSESUSED - the number of licenses that filePro shows to be
        currently in use.

    PFPROCESSCOUNT - the number of license-counted programs that filePro
        shows to be currently running this may be higher than the number
        of licenses used since multiple sessions with the same session
        id will only use one license count.

(Windows) #1114
        fP-SQL would crash when opening an ODBC alien file.

(All) #1115
        fPcopy would crash on a very long filename.

(Windows) #1116
    If the code:
         handle = new odbc_connection(dsn) failed due to a license
         failure, "handle" would remain unchanged. The typical symptom
         would be seen as "odbc_conection returned a blank value".

=========================
5.6.08 Release Notes
=========================

(Windows) #1016
    ddefine did not allow filenames with "." in Windows
   
(Linux) #1018
    showlock did not display all locked records Linux
   
(All) #1026
    Only one index was deleted when selecting multiple indexes in ddir/dprodir
   
(All) #1072 - enhancement
    GETENV("PFREADONLY") will now return "ON" if the "-ro" flag is used, even
    if not set in the environment.
   
(Quickstart) #1075
    If you have a label "foo" and another "foo-bar" (ie: the same prefix, with
    a hyphen and a suffix added), references to "foo-bar" would refer to "foo"
    if "foo" occurs earler in the processing.

(All) #1068
    If you had something following the "b=(expression)" part of a browse
    lookup which "looks" like part of a valid expression, filePro would
    take that as part of the "b=(expression)" part of the browse lookup.
   
    For example:
   
        lookup foo k=xx i=a -nx b=(brwhead&brwdata)          *2"
   
    (If, for example, you were to edit the lookup line to remove a literal
    browse lookup, and missed the trailing "*2".)

(All) #1021
    In dcabe, if you load a processing table with a DECLARE GLOBAL and syntax
    check it, and then load and syntax check another processing table which has
    the same DECLARE GLOBAL name, but a different definition, you would get an
    "already defined" warning.
   
(All) #1040
    EXIT in @ONCE processing didn't exit *report.

(Linux) #974
    Website didn't allow license to be downloaded when using Domain Name
    as the license check value for Linux systems.

(All) #975
   The following flags have been added to swapcpu:

    -Q  = Quiet mode.  Suppresses "file already in destination order".
    -CN = Convert to native byte order.
    -CF = Convert to foreign byte order.

(All) #977
    swapcpu didn't swap the "blob" file.

(All) #982
    PFMBTO only caused the first message box to time out.  All subsequent
    message boxes still required Enter.

(Windows) #1016
    On Windows, ddefine did not allow you to create or access files with
    a dot in the filename.

(Linux) #1071
    On some systems, a fresh filePro install would fail with "fatal error
    check current user count: invalid argument".

(All) #1077
    filePro 5.6 is now available on FreeBSD.

(All) #1088
    Calling READLINE() with an uncast dummy field, which has never been
    assigned a value, and not including a maximum length, could crash
    filePro.

(All) #1099
    There was a memory leak in nested CALLs which has been fixed.

(All) #1100
    Under some circumstances, filePro would not use the available free
    space in the blob file for new blobs/memos, causing the blob file to
    grow larger than needed.

    Note that the updated blobfix utility can be used to "fix" this, and
    shrink the blob file to the "correct" size.

(All) #1101
    If you have a lookup to a file that has an automatic index built on
    an associated field group, but the lookup is not on that index, it
    was possible for filePro to crash.

(All) #1102
    Executing a LOOKUP in a processing table, CALLing another table
    which executes a LOOKUP to the same file, and then CLOSEs that
    lookup, can cause filePro to crash and/or give unusual errors
    upon re-executing the LOOKUP in the original processing table.

(Linux) #1103
    The Linux distribution included an old "lib/rename" utility, which
    wouldn't run on some current Linux distributions.

(*nix) #1014
    User-count debug logging can now be controlled via the new config
    variable "PFCHKUSER=logfilename".

(All)
    xfer now handles the blob file.

(*nix)
    filePro could crash in some debugging modes of the system environment
    variable MALLOC_CHECKS.

(*nix) #1070/#1096/#1097/#1098
    Some places in filePro didn't properly require double-break.

(*nix)
    Debug versions hard-coded the user-count logging filename.  This is
    now controlled with PFCHKUSER=logfilename.

(All)
    OPENDIR() could crash if given a directory with thousands of files,
    all in alphabetical order.

(All)
    If a user menu's title and version number filled the space allotted,
    filePro could crash.

(*nix)
    On some *nix systems, DEL (when not used as the Break key) would not
    be treated as a backspace.

Logged

Bill Randall
Pages: [1]   Go Up
Print
Jump to:  

Valid XHTML 1.0! Powered by SMF 1.1.15 | SMF © 2011, Simple Machines | Massive Blue Theme By Cadosoas Valid CSS!