[AccessD] Plotting datapoints to Excel

Hi Charlotte:

I have done some great charting and graphic layout and designs using the
Google Chart tool: https://developers.google.com/chart/

It is web based though but with a bit of work some fairly nice 3D effects
with third party products like: http://www.jfree.org/eastwood/ or you can do
some nice 3D effects by staggering and stacking layers in a web page. (I did
this so a client could see a number of years at once.) It is also easy to
print to any printer on the network. 

If you want to spend a little money there are dozens Google chart add-ons
like: http://www.dmxzone.com/go?14928

...and then there is the free version of Adobe Edge for more 3D and
animation: http://tinyurl.com/6adgd4t

With VS it should be easy to mix modes and switch from desktop to full page
browser displays. All it needs is an intranet and an IIS version on the
server with ASP.Net installed. 

This mixed mode works very well for slowly weaning a client off desktop
dependence.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Tuesday, May 08, 2012 7:28 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Plotting datapoints to Excel

The source of the problem is the state requirements.  We are required to
submit the report using their template.  Their template is designed to
resemble other lag reports we produce for this particular state, and which
are produced fairly easily.  This one only looks something like the others
and there's nothing easy about it.  The "logic" behind it makes my head
ache.  We are contractually obligated to do it this way and to be as
accurate as possible.

It definitely is cube data in a 2-dimensional report and I can't change
that.  Apparently there are folks on the receiving end who use this data,
so all I can do is try and find a way to make producing it less torturous
for the users.  We are reading data out of a formatted text file, adding to
it where possible, eliminating some claims based on rules, and then slicing
and dicing data into the categories in this worksheet to the best of our
understanding of their requirements.  Did I mention the data comes in
weekly or monthly and the reports are quarterly by month?  Sound like fun?

Charlotte Foust


On Tue, May 8, 2012 at 5:01 AM, Susan Harkins <ssharkins at gmail.com> wrote:

> Well, something I tell people occasionally is this -- is the solution is
> too convoluted and difficult, maybe you need to reconsider the problem at
> the source. Maybe the problem at the source could be reworked -- probably
> not... you're dealing with the state right? :( It sounds to me like cube
> data in a 2-dimensional report.
>
> If the data comes through consistently, would it be easier to just dump
> into Excel and rework there?
>
> Susan H.
>
>
>
>  No, the data is pulled from a mainframe report.  The sum of the costs
>> avoided/recovered is entered at the intersection of the month/year the
>> claim was filed and the monthyear the claim was denied or cost was
>> recovered.  Believe me, the documentation is even more confusing.
>>
>> Charlotte
>>
>>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
>
http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadviso
rs.com/mailman/listinfo/accessd>
>
>
> Website:
http://www.databaseadvisors.**com<http://www.databaseadvisors.com>
>
>
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com