I'm not familiar with the stock Help Desk app, but this looks odd to
me... What are the enum values for the Status, and if you are excluding
Resolved and Closed via <>, I just don't like that. If resolved and
closed are right next together and they have an enum value of 3 and 4,
then ('Status' < 3 and 'Status' > 4). If they are not next together
then you could say something like ('Status' = 0 OR 'Status' =1 OR
'Status' = 3). Break up the dates like ('Create Date' >= "12/01/2007"
AND 'Create Date < "12/14/2007"), dates are from midnight unless
specified, so be inclusive on the lower date and exclusive on the latest
date. If you are macroing it, set those puppies up as variables and
dump them as csv's then merge the spreadsheets. If you are trying to
catch over a 1000 tickets for one day then do something like: ('Create
Date' >= "12/01/2007" AND 'Create Date < "12/01/2007 12:00"). I could
go on, but we probably need more details on this ODBC connection, is it
giving you fits outside the realm that I've addressed?
Darrell E Reading II
Contact Center Development
Wal-Mart
45739
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
##################
##################
##################
##################
##################
##################
##################
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Martinez, Raul (ISD, IT)
Sent: Friday, December 14, 2007 10:34
To: [email protected]
Subject: Re: Remedy SQL query assistance... Please Help.
**
Yes there is a limitation in affect right now on the server. Here is an
example of what we are doing, but of course the code is not 100%
correct:
said syntax error
?
SELECT "HPD:HelpDesk"."Assigned To Group+", "HPD:HelpDesk"."Assigned To
Individual+", "HPD:HelpDesk"."Assignee Login Name", "HPD:HelpDesk"."Case
ID+", "HPD:HelpDesk".Source, "HPD:HelpDesk".Status,
"HPD:HelpDesk"."Submitted By"
FROM "HPD:HelpDesk" "HPD:HelpDesk"
WHERE ("HPD:HelpDesk"."Assignee Login Name"='Jack Zaldivar') AND
("HPD:HelpDesk".Status<>'Resolved' And "HPD:HelpDesk".Status<>'Closed')
AND ("HPD:HelpDesk"."Create Time"<SYSDATE)
ORDER BY "HPD:HelpDesk"."Case ID+"
11:11:11 AM
?
that's just an example
11:11:23 AM
?
not what we REALLY want
11:11:30 AM
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso
Sent: Friday, December 14, 2007 11:08 AM
To: [email protected]
Subject: Re: Remedy SQL query assistance... Please Help.
** I think he mentioned that the SERVER has been limited to 1000.
On Dec 14, 2007 11:03 AM, Evans.Randy <[EMAIL PROTECTED]>
wrote:
**
Change your preferences to unlimited while you run the macro. You
probably don't want to go against the database itself. Remedy has a
tendency to store dates as long integers based on the number of seconds
since 1/1/1970.
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Martinez, Raul (ISD, IT)
Sent: Friday, December 14, 2007 9:47 AM
To: [email protected]
Subject: Remedy SQL query assistance... Please Help.
**
Can anyone assist me in either in connecting an ODBC connection to
Remedy through Access or with creating a SQL search query for $DATE$
function? I am needing to grab all submitted tickets for current day
based on certain submitters. I already have a remedy macro created but
it would be easier with a SQL query. I had to split the macro up several
times due to the server being limited to only 1000 line return.
************************************************************************
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution
is
strictly prohibited. If you are not the intended recipient, please
notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
************************************************************************
*
__20060125_______________________This posting was submitted with HTML in
it___
__20060125_______________________This posting was submitted with HTML in
it___
__20060125_______________________This posting was submitted with HTML in
it___
__20060125_______________________This posting was submitted with HTML in
it___
-----------------------------------------
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the individual or entity to whom they are
addressed. If you have received this email in error destroy it
immediately.
**********************************************************************
Wal-Mart Confidential
**********************************************************************
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
