2/23/2002 Changes in going from 2.6f to 2.6g:
1. Changed macro detection code ( IN.MACRO ) so that in reports
DP lookups can be accommodated by using the shell macro code 
{PAUSE KEY}{Enter}~{Enter}
2. Changed the WP output mode so that characters 31 and 127 are 
surrounded by the "protection" codes, and the page formatting
codes are no longer generated unless the output is going to 
DPPrint.
3. Changed the processing of Eliminate Line if Blank so that 
it is killed by print or file on/off commands.  If an ELB action
is desired, it should be activated after these commands.

There are a couple of other bug fixes, but nothing I think I need to note.

================================
Version DP26E is the official Y2K release.  June 24, 1999
I have tested it somewhat, but classify it as a beta version until more 
users can help me look for bugs.  There are many changes, so I'm not at 
all confident that adequate testing has been performed.

The specific Y2K change is the addition of the "rollover" option for all
date fields.  However, it is only active during data entry if the date field
format has only 2 digits for the year.  If you specify a non-zero value for
the 2 digit "rollover" value, the year of the entry is compared to it.  If 
the rollover is more than the entry, the entry is added to 2000, otherwise 
to 1900.  Thus, if the date format is D99/99/99 and the rollover value is 
50, 01/01/49 is 01/01/2049, while 01/01/50 is 01/01/1950.

The rollover option has no effect on previously entered data.
The rollover option has no effect if the year is entered with 4 digits.

The rollover option is active while importing data.  This can be used to
to correct data entered prior to the availability of this opion, BUT PLEASE
use it carefully -- save your data before hand and check that it worked as
you intended.

This required changes to DPEXP, DPIMP, and STE-MGR.

For my own use, I will continue to use 4 digits for the year, and recommend 
that to others also.  Where 2 digits is deemed essential, I recommend a 
rollover value of 80 for forward, ongoing dates.

There is also a new date format.  Here is the "help" description:

  The "new" date format also begins with a "D."  This date format MUST
  contain no "9" digits.  It should have none or 2 "D" characters for
  the day and none or 2 "M" characters for the month.  The other
  alphabetic character, whatever it is, will be used for the year.
  The year character selector should occur none, two, or 4 times.

Examples are DMMDDYYYY  DDD/MM/AA
This editor behaves quite differently than the editor for the standard 
date fields.  You should play with it and determine if you like it better.

There is a new startup entry: /ind
It causes the indexes to be regenerated.  It requires that the database 
name also be supplied on the first line, or that a runtime version is 
being used that incorporates the database name.  Please give me feedback 
regarding how this works for you and if it requires changes.  I have not 
added this option to the help displays as of yet.  With this (and with 
index regen from a menu, below,) a password is not requested if all you 
have specified is a definer or definer/supervisor password.  If a user 
password is specified, index regeneration requires at least that password.

There also is a new menu option for regenerating indexes.  Once again, 
usage feedback is requested.

I'm sorry this version does not include more new things.  I'm still 
studying more extensions, but in the near term I'm returning my attention 
to a Windows program that will allow us to move in that direction.

===============================
Version DP26D is a bug fix version. Jan 21, 1999
Convert[] was broken and is now fixed.
There is another bug fixed, but I regret to say I can no longer remember what 
it was!  It was minor, but I fixed it and lost the note.
I'm still working on additional features for this program as well as two new 
programs - a Windows GUI and an Internet CGI.
Lew Bastian
===============================
Version DP26C is a bug fix version.
It fixes text editing bugs introduced when the text editor was partitioned 
to enlarge the work space.
It fixes the failure of ICAPS to capitalize after a carriage return.
It also has significantly more work space in an effort to eliminate the
memory error 104.  THIS SPACE WAS OBTAINED BY PARTITIONING THE FORMULA 
EVALUATION CODE.  ALL FORMULAS ARE TO BE TREATED AS SUSPECT.  PLEASE HELP 
ME TEST FORMULAS BY GOING THROUGH AS MUCH OF THE OPERATIONS AS POSSIBLE.

Below is readme prior to this version:
====================
Here is a new version, DP26B.  It includes file DP26B.EXE (which should be 
renamed to DP.EXE when you install it,) DP.SYS, DATA.MSG DPEXP.COM, DPIMP.COM, 
and STE-MGR.COM.  I believe these are now all synchronized for features.

The new features are:
LPT3, LPT4, COM3, and COM4 are now supported.

Many developers have requested a way to selectively show panels in the panel 
list.  In this version, panels are omitted if the panel name begins with [ 
and the the password state is other than "definer" or "supervisor."  (If 
no passwords have been defined, or if only a definer password has been 
defined, the panel will still always show in the list.)

The name "DataPerfect" has been replaced almost everywhere in DP.SYS with the
phrase "the program."  This change means that, when you use the /RUN option,
no copyright is ever displayed and the user never sees "DataPerfect."  You
are free to call the application whatever you want by renaming DP.EXE and 
DP.SYS.  (See below.)
(Translators: It's easy to see where I've changed DATA.MSG by simply searching 
your current version for DataPerfect.  Very few other changes.)

There is a /RUN option which produces a run time version.  This is a little
different than previous run time versions:
  1.  You supply the name of the user structure file.
  2.  You may change the name of the expected DP.SYS file.  If you do this.
      you are expected to copy DP.SYS and DP.EXE and give them the new names.
      This allows you to give the user an application completely under your
      control.  It can't be used to access any other database.

============================
Note: MCREATE.COM reads DATA.MSG and creates DP.SYS.
These files are used to translate DP to languages other than English.
I decided to make them generally available.
Those with a "need to know" have already received instructions,
but it's a simple format and you should be able to figure out what's going
on in DATA.MSG.  If you have questions, I'll try to answer them.

============================
Here are the notes for DP2.6A:

This new version of DP includes a fix for the bug in DP255E and two new 
functions, LOWER.CASE[arg] and ICAPS[arg].  (This last function capitalizes 
the first letter of each word.)

DPEXP and DPIMP both have a new command line flag /Q which stands for "quick." 
The displayed text is markedly shorter, which increases the speed dramatically 
on today's newer machines.  However, if you have errors, you will need to 
leave off the /Q in order to see where they occur.

DPEXP has an additional flag, /E, which stands for nothing -- it's just a 
letter!  It causes the formulas to be decompiled.  This is of little use to 
anyone except the foreign language contingent (who are Europeans -- now you 
see where the /E comes from!)  Ordinarily DPEXP exports the text for formulas 
as it was entered.  This means, however, that the language inside the formula 
is not translated even if the formula section of DATA.MSG (used to produce 
DP.SYS) has been translated.  In the past this has meant that our foreign 
language users have been forced to use the english names for functions.  
(Long ago I shipped a version of DPEXP called DPEXPE.COM to take care of 
this.)  If you use the /E option and the DP.SYS file has the function names 
translated, the comments will be lost, but the formulas will be translated 
for valid formulas.  
(Invalid formulas will still use the text as entered, since the compilation 
failed.)  
Foreign language users please note, I do not necessarily recommend translating 
the structure export / import section of DATA.MSG  that begins with message 
238.  If you leave these alone, you can safely export and import any .STE 
file without regard of the version of DP.SYS you're using.  Otherwise you 
have to be careful or you may blow your .STR file away.  However, if you want 
to do it, the capability is there.

Lew Bastian
