DWUTKA at marlow.com
DWUTKA at marlow.com
Wed Dec 21 15:09:49 CST 2005
Okay, how about 'Yes, I have LOADS of experience do this kind of stuff'. You didn't really ask many technical questions. I would recommend setting up an in house IIS server for them. Preferably, move the database to that IIS server. If you are going to build an external interface for the database, you might also want to look into building an internal ASP interface as well, which will vastly improve performance. Feel free to ask for help, just need more direct questions if you want a more useful technical answer! ;) Drew -----Original Message----- From: John Colby [mailto:jwcolby at colbyconsulting.com] Sent: Wednesday, December 21, 2005 2:52 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Serving reports to the web LOL. Technically correct but totally useless. Even I know enough to say ASP. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com Sent: Wednesday, December 21, 2005 3:30 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Serving reports to the web Um, ASP? Drew -----Original Message----- From: John Colby [mailto:jwcolby at colbyconsulting.com] Sent: Wednesday, December 21, 2005 2:16 PM To: 'Access Developers discussion and problem solving'; Tech - Database Advisors Inc. Subject: [AccessD] Serving reports to the web 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/ -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com