On 08/27/2010 11:02 AM, Daniel Lewis wrote: 
>      I am presently beginning the SQL section of Chapter 4 of the Base
> Guide. (Progress report of sorts) 
>      In the Query: Using Design View section, I ran into a problem
> went explaining what search conditions (Criterion and OR rows) are
> available and the format they require. As a result, I am suggestion an
> appendix be written listing several of them, preferably the ones used
> fairly often but not in the format most would know. 
> 
> Ex.: 
> 
> NOW() is used in Calc to enter today's date or today's time stamp.
> However, CURDATE() and CURTIME() are used in a query to search for
> today's date and the current time respectively. 
> 
> BETWEEN ... AND ...  as a search condition searches for a range.
> BETWEEN #05/17/08# AND #09/30/09# searches for all dates from
> 5/17/2008 to 09/30/2009. This can also be written BETWEEN '2008-05-17'
> AND '2009-09-30'. 
> 
>     Many of these can be found in the hsqldb guide.pdf (HSQLDB Guide).
> I'm thinking the more important ones should be included in the
> proposed appendix rather than requiring people to search through the
> PDF file to locate what they need. 
>     It would be nice if some one or some people acquainted with the
> search conditions of of other database programs could list for me the
> search conditions most often used in them. Then I could research
> possible differences and add them to the appendix. Knowing the more
> common search conditions used by people in Base queries would help
> also. 
> 
Hello Dan, 

Well, I am not really sure what you are after here. 

If you mean common criteria then I'm not at sure how to respond. 

Are you just asking for a list of functions? 

Do you want some scenarios - End of Month Reports, All employees needing
a review - that type of thing and an example of how someone might
construct such a query? 

Drew 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to