>I think Flores' answer is excellent; I use that method(?) too.
>However I have more tip and question about implementing M.S graph.
>
>Tip1.
> ** Using Autoformat property.
>
> If there is no predefined max value of data series, that is to say whenever a your makes
> graph in applications the max value fluctuate emensely, user may get stupid graphs that
> every data value for graph exceed the max limit of predefined graph in Gen field.
>
> Autoformat property can solve this problem.
>
> < code omitted >
>
> Use Utiltable
> Append General gen_1 DATA m.Cgdata ** m.Cgdata ; data series
>
> Thisform.oleboundcontrol1.ControlSource = " gen_1"
>
> Thisform.oleboundcontrol1.autoformat(n,m)
>
> The combination of numbers n,m in autoformat(n,m) decide which types of graph it would be
> and you don't have to worry about the value of X,Y axies. But the combination is also predefined
> that if you issue the wrong combination it can cause an error.
>
>Tip2. Covering Oleobject with transparent shape object.
> This can prevent users from making dubleclick event on the Oleobject; in case Activating
> Ole server application is not desirable.
>
>My Question.
>
> A client PC has no M.S graph and M.S graph runtime is included in the setup procedure. But
> the graph in application is not working. Does anyone know why ?
>
> Thanks in advance.
You're right about that problem that can arise when predefined graph is given a larger set of values than the test data you use. I mentioned that approach as quick and dirty solution for John's problem. I also stated I had to go to OLE automation to get a better grip on the layout of a graph. You've made a good point on using the autoformat method of MS-Graph. But even this does not give you the solution to everything a user may ask for.
In addition to your number 2 tip, you can also set the OLE bound control Enabled property to .F., to prevent users from double-clicking on it and activating another application.