> Hi Mike,
>
> I have used the previously given FUNCTION SqlProgress(lbShowProgress) thus far with the result I want.
>
> I also want to try your OOP approach.
>
> I put the define code in the prg file that I run the 'Big' SELECT routine in.
>
> I also added the code as you suggested
>
> LOCAL m.loThermo
> m.loThermo = NEWOBJECT("cusSQLThermo","cusSQLThermo.VCX")
>
> SELECT ..... etc - my big select
>
> RELEASE m.loThermo
>
> However no object is created as seen in the debugger.
>
> I wonder about the '"cusSQLThermo.VCX")' in the NEWOBJECT statement.

I do not do what most do. Most make a vcx with many unrelated things in it. I wonder how does this thing relate to other things in a system. Since there is little benefit to arbitrarily combining things, I stopped long ago. Now, when I need something I just tell FoxPro to get it. Unfortunately the VCX cannot be ignored. I name the vcx the same as the class so I don't have to think about it at all. I just name things properly - which has to be done in any case, and I'm home free.



>
> Some things that are clear to experts leave others puzzled - Mea Culpa!
>
> Have you any clarification as to how to make the class work please.
>
>
> -Bryan

Wellll, I'm not sure whose fault it is. I expect all programmers should understand the code in the sample explains that this is supposed to be a new visual class based on the VFP custom class. It's easier to show the code this way than to attach a zipped vcx file. So start up your class designer and make a new class based on custom. Add the properties icoldsettalk etc, and make them protected. Copy the method code into the methods. Save the class as cussqlthermo into a vcx called cussqlthermo.

Mike Yearwood
Microsoft MVP Visual FoxPro 2008



We have enough youth. We need a fountain of smart!
There may be many ways to skin a cat, but there are very few right ways to do it.