p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

sql_language thread: SQL 6.5 Query


Message #1 by Nigel Parker <Nigel.Parker@c...> on Wed, 20 Mar 2002 12:08:09 -0000
Hi Richard

thanks very much, it was the date criteria that was causing the problem!

regards

nigel

> -----Original Message-----
> From:	Richard Hadfield [SMTP:Richard.Hadfield@o...]
> Sent:	20 March 2002 12:41
> To:	sql language
> Subject:	[sql_language] RE: SQL 6.5 Query
> 
> Not sure but try:
> 
> SELECT 
> 	InTray.USER_ID, 
> 	InTray.MAIL_STATUS, 
> 	InTray.DATE_PEND
> FROM 
> 	Document 
> INNER JOIN InTray ON (Document.GUID = InTray.GUID) AND (Document.GUID 
> InTray.DOC_GUID)
> 
> WHERE 
> 
> ((InTray.USER_ID='UserNameHere') AND 
> (InTray.MAIL_STATUS='P') AND
> (InTray.DATE_PEND >'2/21/2002')) 
> 
> -----Original Message-----
> From: Nigel Parker [mailto:Nigel.Parker@c...]
> Sent: 20 March 2002 12:08
> To: sql language
> Subject: [sql_language] SQL 6.5 Query
> 
> 
> Hi
> 
> Can anyone tell me how convert this query to work with SQL 6.5.
> The DATE_PEND is a date time field.
> 
> SELECT 
> dbo_InTray.USER_ID, 
> dbo_InTray.MAIL_STATUS, 
> dbo_InTray.DATE_PEND
> FROM 
> dbo_Document 
> INNER JOIN dbo_InTray ON (dbo_Document.GUID = dbo_InTray.GUID) 
> AND (dbo_Document.GUID = dbo_InTray.DOC_GUID)
> WHERE (((dbo_InTray.USER_ID)="UserNameHere") 
> AND ((dbo_InTray.MAIL_STATUS)="P") 
> AND ((dbo_InTray.DATE_PEND)>#2/21/2002# )
> 
> This was used in access 97 and I need it to run in SQL Query Analyzer in
> SQL
> 6.5
> 
> Thans to anyone whom may help
> 
> regards
> 
> nigel
> 
> 
> 
> 
> 
> NOTICE AND DISCLAIMER:
> This email (including attachments) is confidential.  If you have received
> this email in error please notify the sender immediately and delete this
> email from your system without copying or disseminating it or placing any
> reliance upon its contents.  We cannot accept liability for any breaches
> of
> confidence arising through use of email.  Any opinions expressed in this
> email (including attachments) are those of the author and do not
> necessarily
> reflect our opinions.  We will not accept responsibility for any
> commitments
> made by our employees outside the scope of our business.  We do not
> warrant
> the accuracy or completeness of such information.
> 
> 

  Return to Index