[dba-Tech] Serving reports to the web

John Colby jwcolby at ColbyConsulting.com
Fri Dec 30 09:55:27 CST 2005


My client downloaded a demo of Iron Speed, which is a web site builder that
understands databases.  He was quite pleased with what he could do given his
relative lack of expertise in the subject.  I have not tried it myself yet.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/
-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Tina Norris
Fields
Sent: Saturday, December 24, 2005 9:02 AM
To: Discussion of Hardware and Software issues
Subject: Re: [dba-Tech] Serving reports to the web

I will be very interested in knowing more about this, too, although my
application is nowhere nearly so large, or complex, or confidential. 
 Mine is a database of water quality sampling events and analysis results,
with a log of volunteers' time (valued as matching funds in-kind to a
grant).  The quarterly report on volunteers' time is part of the invoice
sent back to the granting agency.  While the database was kept on a single
computer, the report was generated, and saved as a pdf file for electronic
transmission.  Now, the database is on a website, and the html report does
not give the same pagination - I don't know how to turn it into a printable
report that looks like the one I made when the database was just here on my
box.  This database web site stuff is a new realm for me.  I will stay
tuned, and I'm glad John asked the question - I was too timid.
Tina

John Colby wrote:

>Does anyone have any knowledge of what is required to serve reports to 
>users on the web.
>
>The scenario is the Disability Insurance call center, a new client, 
>which wants to get access to summary information on insurance claims 
>being processed for management, but eventually to allow claimants to 
>see the status of their claim live, online.
>
>I need a feel for how the security issue is handled, how users / 
>passwords can be created automatically, and once created how reports 
>can be generated and displayed based on the user logged in.  Details 
>are sketchy, but I am guessing that a secure area would be created 
>where users log in.  The first pass would segment the users into 
>claimants and managers.  Once logged in, a selection of possible 
>reports (assuming that once demonstrated, the reports will grow
uncontrollably).
>
>The BE is currently an Access BE approaching 500 mbytes, pounded on all 
>day by ~40 users live in-house entering claims and answering calls.  
>How does a web enabled app get data out.  The "boss" has already pretty 
>much nixed emailing reports and downloadable predefined PDF files.  
>Which to me indicates they are looking at "configurable" reporting out 
>of live data, straight to html, with strong security to keep the wrong
people out.
>
>Anyone out there with experience in doing this kind of stuff?
>
>John W. Colby
>www.ColbyConsulting.com
>
>Contribute your unused CPU cycles to a good cause:
>http://folding.stanford.edu/
>
>_______________________________________________
>dba-Tech mailing list
>dba-Tech at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-tech
>Website: http://www.databaseadvisors.com
>
>  
>


_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com




More information about the dba-Tech mailing list