C / C++ / MFC

if( pView != NULL )
{
    if( pView->m_list1.GetSafeHwnd() )
    {
        // do stuff
    }
}

"The significant problems we face cannot be solved at the same level of thinking we were at when we created them." -Albert Einstein

Syntax
match_expression [ NOT ] LIKE pattern [ ESCAPE escape_character ] 

Arguments
match_expression

Is any valid SQL Server expression of character string data type.
...

--CONVERT ( data_type [ ( length ) ] , expression [ , style ] )
select CONVERT(varchar, DateField, 103 ), DateField From SourceTable

0 or 100 Default mon dd yyyy hh:miAM (or PM) 
1 or 101 USA mm/dd/yy 
2 or 102 ANSI yy.mm.dd 
3 or 103 British/French dd/mm/yy 
4 or 104 German dd.mm.yy 
5 or 105 Italian dd-mm-yy 
6 or 106 - dd mon yy 
7 or 107 - Mon dd, yy 
8 or 108 - hh:mm:ss 
9 or 109 (*)  Default + milliseconds mon dd yyyy hh:mi:ss:mmmAM (or PM) 
10 or 110 USA mm-dd-yy 
11 or 111 JAPAN yy/mm/dd 
12 or 112 ISO yymmdd 
13 or 113 (*)  Europe default + milliseconds dd mon yyyy hh:mm:ss:mmm(24h) 
14 or 114 - hh:mi:ss:mmm(24h) 
20 or 120 (*)  ODBC canonical yyyy-mm-dd hh:mi:ss(24h) 
21 or 121 (*)  ODBC canonical (with milliseconds) yyyy-mm-dd hh:mi:ss.mmm(24h) 
126(***) ISO8601 yyyy-mm-dd Thh:mm:ss:mmm(no spaces) 
130* Kuwaiti dd mon yyyy hh:mi:ss:mmmAM 
131* Kuwaiti dd/mm/yy hh:mi:ss:mmmAM 

*    The default values (style 0 or 100, 9 or 109, 13 or 113, 20 or 120, and 21 or 121) always return the century (yyyy).
** Input when converting to datetime; output when converting to character data.
*** Designed for XML use. For conversion from datetime or smalldatetime to character data, the output format is as described in the table. For conversion from float, money, or smallmoney to character data, the output is equivalent to style 2. For conversion from real to character data, the output is equivalent to style 1.

select DateFieldFrom SourceTable
Where CONVERT ( varchar , DateField, 121 ) like '2002-11-05 [0-1][0-4]%'

<br />
m_wndMyControl.SetFont( GetFont( ) );<br />