I have forwarded the latest versions of DP to Udo. Here's the
accompanying info about it I got from Lew:
---
I think I've fixed the bug -- actually DP was working as designed but it
should have been better, so now I think it is. I hope users will test
this and report any more troubles to me.
Attached is the zip file for a new version. It includes a .TXT file
with the following text.
May 2009 -- but part of development done in 2008.
Dear friends of DataPerfect.
NOTE: This zip file contains two versions of DP26Y:
DP26YU.EXE corresponds to the normal version.
DP26YI.EXE is identical except that report formats for HTML produce
italic codes rather than underline codes.
I recommend copying DP26YU.EXE to DP.EXE for normal use.
After a long delay, here is a new version of DataPerfect, DP2.6Y.
I've cleaned up a few things, but the only real changes are to
(hopefully) make it more useful as a command line web application.
Three major changes:
1. New design for "Eliminate Line if Blank" that I hope fixes all the
problems
people have had with this in the past.
2. Fixed the bug that caused transaction log imports to end after running a
report. So now you can include multiple #R sections to run many
reports.
3. VERY IMPORTANT: When you run DP with a /EI transaction log import, the
"screen" or "display" output is sent to STDOUT, the DOS, WINDOWS, LINUX,
etc. standard output file. Nothing will show up on the screen, but
if you
do an output redirection, that output will be redirected. Thus the
command line:
dp database.str >report.out /ei=trans.log
will open database.str, read and process trans.log, and any report
output
will be written to report.out. Of course, if the reports specify any
other
file writing, that will be written as before.
The use of STDOUT should make DP much more useful as a scripting engine.
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
