I just sent a copy of this to Lew. Brian Hancock wrote: > 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
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
