>Cesar
>
>I've placed the line just before the Drawchart() method, but unfortunately that hasn't cracked it.
>
>I've found another progress bar class by Craig Boyd
>
>
http://www.sweetpotatosoftware.com/spsblog/CommentView,guid,87d20512-82d6-4ab2-827f-13a1bb5bbbf4.aspx>
>that I'm hoping doesn't suffer from the same problem, but it would be great to crack this though.
>
>Thanks for your help so far,
>
>Kind regards
>
>Rob
>
>>>Ok, many thanks for your help
>>>
>>>>My guess is that FoxCharts and ctl32_progressbar as stepping on each other somewhere in the area of binding to Windows messages. You'll have to dig deeper to resolve the problem.
>>>>
>>>>>I'm using the latest version.
>>>>>
>>
>>
>>Robin, just for an experiment, I'd like you to make a change in a single property in FoxCharts -
>>Please adapt the code below to your case and tell me how it goes !
>>
>>
Thisform.FoxCharts1.ChartCanvas.RenderMode = 1
>>
>>Make sure to change that property value before calling the "DrawChart()" method !
>>
>>HTH
>>
>>Cesar
Thanks for testing !
But wait, was it working normally without using FoxCharts ?
I use the ctl32 controls a lot here: the "Scrollable container", the "ProgressBar", the "slider" and the "calendar control", together with foxcharts, even in the same form, without any problems.
You might be using another utility that binds Windows Messages.
Do you use Emerson Reed's "Themed controls" ? Or Anatoly's transparent menus ? Or Herman Tan's "OwnerDrawn menus" ? These utilities could cause conflicts as well.
As I told you, I never faced any problems with it. Maybe you're not using the latest version from the CTL32 ? I know they received some cool implements, using the VFP2C.FLL from Stefan Ehlcheidt.
