Yep. Exactly the same intent, but more useful, actually. This way you have system information globally available.
And thanks for the kind words in your previous post, Brian. Ralph On 9/18/2010 1:02 PM, Brian Hancock wrote: > Hi Ralph, > > I should have gone back and read before mentioning it. I think the intent is > the same, that you create a report based on a panel that has at least one > record which itself is not the target data for the report, but which is used > as a repository for sub-reports which do the actual work. In my usage there > is no other panel which would be guaranteed to have at least one record. > > In some respect my dummy panel is not so dummy anymore, because I use it for > such things as the domain name, the organisation the application is licenced > to, the licence information, or any other snippets of information that are > global settings for the application. Because it only has one index (based on > a single field with the initial value of 1), it means that in deploying the > application to a new client I can just upload the Panel's data file, and > nothing else changes; plus since it has one and only one record then it is a > good choice for the dummy report. > > Thanks > Brian > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Ralph Alvy > Sent: Sunday, 19 September 2010 12:52 AM > To: [email protected] > Subject: Re: [Dataperf] DataPerfect limitations/suggestions > > The Report Panel, introduced to me by Mark Nepon, referred to in my > previous post, was actually called a Printer Control Panel in my book. > It's a panel where information specific to different printers is stored, > one printer per record. Codes for Bold On, Bold Off, etc., are stored > there. I see why you would want to also put certain Web parameters in > such a panel as well. > > On 9/17/2010 10:48 PM, Ralph Alvy wrote: >> On 9/17/2010 4:11 PM, Brian Hancock wrote: >>> A dummy one record panel that is the report that all web reports are >>> based on. It creates virtual links to the web parameters panel (link via >>> the SID with the DP function user.field[0]. One of the reasons it is so >>> essential, is that if you base a report on a panel which has no data >>> then the report will not run, so adding the first record in a panel is >>> very problematic, unless you use the dummy panel. >> >> Actually, I think my book talks about creating a dummy report (really >> just a dummy report body) from the first record in a panel, and then >> making sure that parent report body stops after exactly one record (all >> the while its various subreports process all the records you want). So >> you don't really need a separate dummy report panel for this. You just >> need a panel that has at least one record. >> >> A Report Panel is another subject altogether, and that was introduced to >> me by Mark Nepon. > > > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
