Hi Lew, Hi Ralph and others Unfortunately the latest May 2009 DP version does not fix the multiple report commands in a single Transaction Log problem.
It works if there are just multiple simple reports. For example a T-LOG with just #R: =4= #R: =2= Will possibly work as long as the first report is not complex. The most likely reason to run two reports from the one T-Log is where you have one "action" report which needs to be followed with a report which outputs a standard report. This allows re-useability of reports. For example you might have the circumstance where the first report saves data back into the database, and the 2nd report produces a listing with the updated data. You might also have another one which deletes a record and then produces the updated listing, or perhaps for inserting (adding) a new record and then producing the listing. The various "action" reports for updating, deleting or adding then chain back to a single output report. With the previous DP version it was necessary to invoke DP twice, once with the action report, and then again with the listing report. The disadvantage of this is the time it takes to start up DP Unfortunately the new version when used with two report commands in the same T-Log causes a corruption of the database when you have a report which updates or deletes data. Regards Brian -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ralph Alvy Sent: Tuesday, 2 June 2009 6:16 AM To: [email protected] Subject: [Dataperf] New Version Now Officially Released > 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 _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
