>>Well, I've had my fill of ActiveX controls in general and the ProgressBar in
>>>particular. So, I created my own Progressbar class that does all the ActiveX
>>>control did and more. It looks better, it's more configurable, it has NO bugs
>>>and it is easily sublcassed.
>>>
>>>If anyone is interested in this class let me know and I'll post it to the
>>>file section.
>>
>>Please do, Michael. I'm fast coming to the conclusion that we shouldn't use OCXs unless there is no other way to accomplish what we need.
>>
>>Barbara
>There is a nice three piece (basic, progress bar with count, progress bar with percent) described in the current issue of FoxTalk including the code. I just dropped this on a form and things worked fine. I have also subclassed the calendar as describe in the M$ Fox area to 'data bind' the control again without problem.
>I'm curious about the 'no ocx' comment. Packages like GraphServer etc seem quite stable. What components have been problematic aside from this thread?

Gary, I am perhaps biased. My experience has been with 2 MS OCXs, MSCOMM32 and COMCTL32 and with a couple of purchased OCXs which said they were VFP compatible, but were not - and had Tech Support people who knew VB and thought it was identical to VFP :-(

I've spent too many hours chasing an OCX that has become un-registered or has been overwritten with a version VFP can't use to be happy.

Barbara