dBASE Programming - Re: Ideas on Design for accessing reports

This is Interesting: Free IT Magazines  
Home > Archive > dBASE Programming > November 2007 > Re: Ideas on Design for accessing reports





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Ideas on Design for accessing reports
Greg Hill

2007-11-16, 1:30 pm

"Lysander" <nobody@nowhere.de> wrote in message
news:Rq5WmLFIIHA.460@news-server...
> Greg Hill schrieb:
>
>
> "Slightly"??
> You must be joking...
> When I started converting to Firebird, it was the great (real great)
> advance in speed that helped me to push through and to force the changes.


I know the advantage. I am talking about my method of getting the data
prepared. Right now almost all of my reports go to a temp file. With FB I
imagine I will be able to prep my data in Views, stored procs and functions
:-). But I am not sure if I want to convert all of that in the beginning.

>
> The least you can get is a performance win of 20-30 %.
> Some of my reports today need 3 seconds where with dBase (_WITH_ local
> temp tables!!!) they needed 3 minutes.
>
>
>
> I put a screenshot of my reportlist module into binaries.
> But I am not reading this group, so any further remarks should be
> discussed here.
> On that screenshot you can see a combobox on top of the left half.
> This CB is filled with possible "report-groups".


Thank you for the screen shot I will take a look.

Greg Hill


>
> In a future release, I plan that users can create custom groups.
> Right now we have predefined groups PLUS the personal favorites with the
> 12 most requested reports.
> I am writing a protocol file whenever a report is viewed, so it is not a
> big deal to supply everybody's favourites.
>
> Whenever a choice is made in the combobox, the listbox on the left half
> get's updated, containing only reports belonging to that group.
>
> Whenever another selection in the listbox is made, the right side shows
> another preview and the bottom displays another description of the report.
>
>
> No, I don't
> To have the PC create a "real" preview for every report every time the
> user takes the leisure to shuffle through all is reports is not efficient.
>
> The preview you see on the screen is a .png made from a screenshot.
> When the user selects another report, another png loaded. C# has a
> built-in support for exporting any region of your form to different
> graphics formats. dBase does not, so you would need snagit.exe or a
> similar tool.
>
> showing only pngs or jpgs means that not any report is called or executed,
> not even a small one with custom data. The pngs are installed to the local
> drive with every new release of the application. When there are new
> reports, but there is no new release, a "noPreviewAvailable.png" will be
> shown.
>
> I also do.
> Previewing a report takes again as much time as just printing or exporting
> it. If the user, based on the PNG-preview, already knows that he chose the
> correct report, no "real" preview is needed anymore; he can directly go to
> print/export.
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com