Andrus,

Mark is right - you are better off using WHERE.

WHERE selects only those records that meet the specified condition and retrieves only those records.

HAVING retrieves all records and then throws away the records it doesn't need. That means you have the "cost" of bringing way too much data over the network.

SELECT ;
    < complex expression > ;
    FROM MyTable ;
    WHERE BETWEEN(MyValue, 1, 1000) ;
    INTO CURSOR MyCursor ;
    ORDER BY MyOrder

>Using having without group by
>
>Is it OK to use having without group by in SQL SELECT ?
>
>I want to place additional filter to result columns,
>like:
>
>Select ;
> as myvalue, ;
> from mytable ;
> having betw( myvalue, 1,100 )
>
> is a very complex expression and i don't wish to include it to having clause second time.