Creating MS Office Graph/Chart in VB App

  • Thread starter Thread starter Ddraig
  • Start date Start date
Cool thanks,

That should get me started but not quite what I am after. I assume that this
would work if I was pulling in information into my app from a Access
Database? My app takes in user data puts it into an access database, then
generate a line graph/chart based on the data. I think I'll sit down and
fiddle with this for a bit. Only info I could find was on the MS Office Web
Component which looked like it might work but couldn't figure it out.

Thanks,
Dd.
 
My best tip is to use Excel and start off from a chart template that you
created manually, but then always save off the template with no series, i.e.
remove all the items from the SeriesCollection either manually or
programatically, then save it, and there you have your template - you can
then add new series as you see fit.
Look at the formula for an existing series so you can glean the format that
the series should be.

That's the hard way.
The easy way is if your data is going to be exactly the same shape every
time, when you can just replace it with new data and the existing serieses
will just update themselves automatically.
 
Hi,

There are also 2 free chart components in the vb.net resource kit.
One from component one and one from dundas charts.

http://msdn.microsoft.com/vbasic/vbrkit/default.aspx


Ken
-----------------------

Cool thanks,

That should get me started but not quite what I am after. I assume that this
would work if I was pulling in information into my app from a Access
Database? My app takes in user data puts it into an access database, then
generate a line graph/chart based on the data. I think I'll sit down and
fiddle with this for a bit. Only info I could find was on the MS Office Web
Component which looked like it might work but couldn't figure it out.

Thanks,
Dd.
 
Thanks for the help everyone, I will definitely check all this stuff out
when I'm implementing the graph portion of the program. I was able to also
find this
http://support.microsoft.com/default.aspx?scid=kb;EN-US;319557

And managed to write a graph using it, and I think I've pretty much got it
all figured out at least how to best implement it. Most of my datafields and
things will remain the same only thing that will change is the data itself
so it seems pretty easy.

Thanks Again,
Dd.
 
Cool thanks, I will probably download this at work on the T1 when I get in
on Tuesday :)
 
Ddraig said:
Howdy,

I was wondering if anyone could point me in the direction of a tutorial or
some information on how to create a chart/graph for a VB application?

Thanks,
Dd.
http://www.fdwsnetworks.com - http://www.tnrgonline.com
I am very impressed with Chartfx. For a simple app you should be able to
use the free version (I am drawing real time graphs so had to pay a swag
of money).
Try
http://www.softwarefx.com/

I have no coneection with the company.
 
Hello,

One advantage of picking VB.NET to develop in, is the large quantity of 3rd
party controls to save you time and energy.

Check out ProEssentials at www.gigasoft.com.

We offer a Lite version for $149, Std for $399, and a Pro version for $1299.
The Lite version will likely handle your needs and provide powerful charting
to embed into your projects. Features like a) optimally utilizing control
real-estate given the chart's shape and data, b) zooming, c) exporting
images and data, d) maximization, and much more.

best regards,

Robert Dede
Gigasoft, Inc.
 
Robert said:
Hello,

One advantage of picking VB.NET to develop in, is the large quantity of 3rd
party controls to save you time and energy.


Hahahahahahahahahahahahaaaaaaaaaaaaaaa


you haven't been in the controls business very long, have you?




Bob
 
Hi Bob,

12+ years. Seems like my entire life. Started with pure DLL interfaces and
next came VBXs, OCXs, and now .NET.

Did you have a bad experience with a component in the past? Not all
components and component makers are the same. Most makers have free
evaluations so you can thoroughly test their logic before buying. Gigasoft's
eval never actually expires. Some makers are truly dedicated to solving your
problems and long-term customer relations. Research is very important.
Looking past the design time and first impressions, and studying the actual
API, and how well that API is rendered. Also consider customer service and
accessibility of support.

Gigasoft also does custom work related to our products. I'd classify us more
as a solution partner than purely a component maker. If a component maker
doesn't offer customer based enhancements and a willingness to resolve your
specific issues, then their component's usefulness is diminished. So before
purchasing a component, ask the maker if customer based enhancements are an
option.

There are definitely components and component makers that can truly and
dramatically cut your costs, energy, and improve your software's overall
quality. Writing/rolling your own is still a valid solution given your
specific requirements, but given the expense, it's best to at least research
all potential components. Using free-ware source is great for simple
implementations, but can quickly turn into a full-proprietary project in
itself if your requirements can grow.

best regards,

Robert Dede
Gigasoft, Inc.
www.gigasoft.com
 
Robert said:
Hi Bob,

12+ years. Seems like my entire life. Started with pure DLL interfaces and
next came VBXs, OCXs, and now .NET.

Did you have a bad experience with a component in the past?


Mostly only in the present, and not so much with controls as with
vendors.

Your initial assertion was that choosing DOTNET gave people the
"advantage" of
MORE controls to choose from.

It's the "more" which forces me to call "bullshit!"


Back in the VB4-5-6 days, VBPJ used to publich whole issues every year
just to
hold LISTS of the available controls. And I'm not talking about the
flimsy 60
pages that VS magazine puts out now. A typical VBPJ was about twice as
thick,
and the special controls issues were the same or even slightly thicker.

Compared to 4-5 years ago, the controls market today has shaken out
badly, with most
of the big names now having either merged with one or more of the
others, or just plain
dissapeared. Sure, some are now putting out dotnet stuff, and some new
players have
entered the field, but I've probably got more OCX controls in boxes out
in my garage
(I used to write controls review articles published in e.g., InfoWorld)
than all the
dotnet controls available *everywhere*



Bob
 
Hello,

I'm well aware of VBPJ in their hay day. We ran full page ads for two years
straight.

MSDN has taken over as the largest print source with ads. Though, the
internet has really hurt all the magazines.

Back when VB4 came out, there was a brief surge as no-one really knew what
to expect as an ROI. Now, the ROI doesn't look so good, so fewer companies
are going for the mass appeal approach (thus fewer print ads). Most vendors
see the money as fair, but the chance of continued success as excellent. You
won't get rich in components, but it's stable if you don't try to grow too
large.

I know the charting market best, and there's more competition now than at
any other point in time, period. This can only help the industry. There are
more product suites available now. More new controls such as PDF exporters,
Shopping Carts, and Report Writers. Especially for .NET.

There are more vendors now, most small focused companies. Some have never
placed an ad in print and have been around for years.

I recognize your concern about shelfware. In my opinion, too many controls
are too generic. They are designed to offer ease-of-use, and do it so well,
the control has little real functionality. I highly recommend thorough
research into the low-level API of any component.

best regards,

Robert Dede
Gigasoft, Inc,
www.gigasoft.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top