Conference bump::msaccess

1657.0. "VERY LARGE REPORTS - Any Suggestions?" by BUMP::CCONLEY () Thu May 08 1997 20:13

    Has anyone had experience with exceptionally large reports?
    
    We have an application that requires reports that run in excess
    of several thousand pages.  The reports have to be saved, and
    the users need to be able to either view or print part or all 
    of prior reports.  The data is somewhat volatile, so the users
    can not re-run certain reports and expect them to be the same
    as when they were originally created.
    
    At present, these reports are generated by COBOL on VMS, as
    conventional COBOL text report files, and the users can view
    them later using standard VMS text editors.
    
    Creating the large reports in "print-preview" mode and printing
    them with MS Access initially seems to be managable; (The users 
    are used to having a private printer tied up for long periods of 
    time)  but saving the reports is more difficult.
    
    If we use the "print to file" option, we can save the reports in
    Postscript format, but they expand to humongous size, and even
    if that could be handled, it is not clear if there is a Postscript
    viewer that can handle 100 Megabyte plus input?
    
    If we export the reports in text mode or .RTF (Rich Text Format),
    we lose some of the report's format structure, and in some cases
    displayed data gets truncated.  Are there any hints for designing
    reports to avoid significant format changes under these conditions?
    
    Viewing very large files is in itself something of a problem, on
    either NT or Windows-95.  MS Word does fairly well, but we haven't
    pushed it to the sizes required by this application.
    
    One final option may be to retain the databases; then allow the
    users to restore specific databases to a "restored" folder and
    then have the capability to re-run the reports.  Thus far the
    users are not keen on that approach, but it is a possibility.
    
    Any suggestions on this will be appreciated.
    
    Chuck
    DTN 223-3926
    

How about creating Make Table Queries, and naming the queries and created 
tables such that you know when the data was analyzed?

Then you will always have the data on hand, and don't have to print the reports 
every time you want to check the data.  And you could even use the same report 
for all of the tables.

    If you can get your hands on it you could look into using Adobe
    Distiller to turn your .PS files into .PDF files which can be viewed
    and selectively printed via Acrobat.  I think .PDF files usually end up
    smaller than the .PS files, too.
    
    	/jeff

    Re: .1  -  Interesting idea.  This may be something we should explore
    with the users.  There may be legal implications in connection with
    this application, so they have to be considered as well.
    
    Thanks,
    Chuck

    Sounds like a good idea.
    
    Thanks,
    Chuck

    re: .3 - no legal implications should exist assuming you are using a
    legit copy of Distiller.  Acrobat is FREE -- the business model seems
    to be to encourage use of it so more people will have reasons to buy
    copies of Distiller!
    
    	/jeff

    That's good to know.
    
    Thanks!
    

The Acrobat READER is free, but the Acrobat Distiller is not. The
READER can be freely (legally) distributed by filling out a simple
form (found on the Adobe Web Site). It allows your users to view 
.pdf files, but not create them. 

Whoever is saving the reports will need the Distiller (about $200).
Once the Distiller is set up, any postscript file placed into one of
it's "watched" folders is automatically distilled into .pdf format. 
A report of 1000 pages would take quite a while to distill,
so think about where you install the distiller!

[Posted by WWW Notes gateway]