>Hello Mike,
>
>On your blog, http://www.foxridgesoftware.com/Blogs/tabid/84/EntryID/2/Default.aspx
>you posted a nifty class, cussqlthermo, that will be useful to me.
>
>DEFINE CLASS cussqlthermo AS custom
>
>Q1: In the list of added properties:
>
> *-- Holds SET TALK setting at initialization.
> PROTECTED icoldsettalk
> icoldsettalk = ""
> *-- Holds SET NOTIFY setting at initialization.
> icoldsetnotify = ""
> *-- Holds the output window at initialization.
> PROTECTED icoldoutputwindow
> icoldoutputwindow = ""
> *-- Holds the name of the temporary output window.
> PROTECTED icnewoutputwindow
> icnewoutputwindow = ""
> Name = "cussqlthermo"
>
>should icOldSetNotify also be protected?

It can be. It's not absolutely necessary, but is good practice.
>
>Q2: In the Init method the window for output is defined off-screen:
>
> DEFINE WINDOW &lcNewOutputWindow. FROM -1000,-1000 TO -500,-500
>
>I take it I'm free to move this so the user can actually see it, right?

I would not. That window is to suppress output like SELECTED x records in y seconds and if a UDF is called in the select, results of variable assignments etc.

Don't you use MaxFrame? You already have the industrial version of this class. I made it for Drew. It's cusPushPopSQLThermo in xxfwmisc.vcx. Oops. Sorry. No, maybe it's in xxfwlibs. Ah, there it is. xxfwutil.vcx