Path: csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!74.125.46.80.MISMATCH!postnews.google.com!o7g2000prn.googlegroups.com!not-for-mail From: Ross Ferris Newsgroups: comp.databases.pick Subject: Re: Time for something new for Excel? Date: Mon, 31 Jan 2011 15:54:46 -0800 (PST) Organization: http://groups.google.com Lines: 61 Message-ID: <170d128f-262d-4437-ac24-ca6e4f0f368b@o7g2000prn.googlegroups.com> References: <1407ed1a-32fa-4534-9a66-7549b3a75e8c@x41g2000prh.googlegroups.com> <4f69ee6e-1812-4fdd-b5ab-5bd8d2a49217@w6g2000vbo.googlegroups.com> NNTP-Posting-Host: 203.89.78.7 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1296518086 26112 127.0.0.1 (31 Jan 2011 23:54:46 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 31 Jan 2011 23:54:46 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: o7g2000prn.googlegroups.com; posting-host=203.89.78.7; posting-account=MrLYOAoAAABU5sRTkSrTdXvmJXwv22kd User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.3),gzip(gfe) Xref: csiph.com comp.databases.pick:2261 On Feb 1, 7:11=A0am, Tony Gravagno wrote: > dawn wrote: > >I will be evaluating what to do for showing users tables online in a > >web page along with options for users to turn the same data into an > >html report, a pdf or download to a spreadsheet. We have only one > >production implementation of an html report, using Cache' Zen reports. > >In theory we can turn this into a pdf as well (just a tad bit of setup > >and also some recoding there). We also have one live spreadsheet > >download. We are using three different approaches for these and might > >need to continue to do that, but we are currently generating the data > >for each separately and with separate specifications, which is not > >cool for keeping them in synch. At the very least we should use the > >same query and at best we would not need to regenerate it. > > General response directed to everyone: > > I think we're getting closer to the question I was trying to ask > originally. =A0Can you give an example of the kind of "tables" that you > need to render? =A0What are people asking for where Zen, PDF, HTML, and > spreadsheets seem to be solutions? =A0Is the request simply for pretty > reports? =A0Dynamic reports that can be sorted or grouped? =A0Intelligent > reports that allow drilling into detail? =A0Do they really want > spreadsheets because they're Excel power users, or might they be > asking for "Excel" because that's a familiar word. > > I'm trying to work out exactly what reporting needs aren't being > satisfied in this market. =A0In some cases people ask for Excel and they > get CSV, which is just one example of where this market falls short. > The real question is - what do end-users need to do their jobs better, > and how can we provide it? > > Excel, static HTML, and PDF might be solutions, but what are the > problems that people are describing? =A0Is "attractive" reporting high > on the list for the people you talk to? =A0Are your users more > interested in different kinds of content? =A0Are they interested in > doing other things with the data that you provide? =A0If so, what > happens to the data that you provide? =A0Maybe we can save people some > time. > > T Tony, FWIW, for "attractive" reporting with Excel we tend to operate with "templates" which already have all the smarts in place in terms of producing graphs, cross tabs, vlookups etc. End user develops & tests these, and we save a "template" of the sheet, sans data .... we then "simply" populate some "data sheets" and we are done. We tend to just pump data in via script from the database, though we can also "drive things backwards", and let people design spreadsheets with data loaded directly from either raw data reads, or by calling specific backend routines (just pass a HTTP reference, including values for named parameters, and Visage middleware will call whatever subroutine with passed parameters, or null/defaults for any missing parameters. As current versions of Excel also allow http references for loading spreadsheets, it then also becomes straight forward to "publish" these base templates so they can be accessed anywhere, without having to do things like mapping shares