>>>>Thanks for the tip, I found the needed description for Visual Basic constants on article Q112671 of the Microsoft knowledge base.
>>>>From my first experience making automation server applications for MSGraph I faced some important facts which maybe useful for any other developer.
>>>>
>>>>One of them is with unbound OLE controls which at the time that are dropped in a form, the “Insert Object” dialog form does not display objects of type MSGraph 5.0 to choose from as long as you have installed any other Microsoft application which installed a newer version of MSGraph like Office’97 (the latest version is the one displayed). The other is with bound OLE controls which are created by declaring the class type. In this case the automation server might create a MSGraph class for a version higher than 5.0. The problem is that when you create distribution disks from the VFP setup wizard, you only have MSGraph 5.0 available to be shipped and probably the coding to control the graphics belongs to a newer version and may not work properly.
>>>>I’m going around this by using a PC with MSOffice installed without MSGraph in order to have MSGraph 5.0 as the latest version.
>>>
>>>What about createobject("msgraph.chart.5") ?
>>>I have not tested but possibly creates a graph 5.0 chart.
>>>Carlos.
>>
>>I´ll try an let you know if it works, Thanks.
>
>Theoretically, the sintax of createobject's parameter is 'application.object.version'. But i don't know if in this case msgraph 8 is overwriting 5.

I tried but unfortunately the created graph is still MSGraph'97 (in my case), I've been recommended to check that OLE class is well registered but how is this done?