You can always set a Character field to $DATE$ + " 5:00:00 PM" and then move that to your Date/Time field Fred
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Monday, April 30, 2007 12:56 PM To: [email protected] Subject: Re: timestamp question (set date and time) ** This should logic should work, unless the date happens to fall on the first day of Daylight Saving Time or of Standard Time, at which point the time set would end up being 6:00 PM or 4:00 PM. Aside from a lookup table, does anyone have any ideas how to prevent this logic from running into problems on those dates? Eric Cleereman -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Wacholz, Jeanette (Jenni) Sent: Monday, April 30, 2007 1:29 PM To: [email protected] Subject: Re: timestamp question (set date and time) ** $DATE$ + (60*(60*17)) should always give you 5pm of the current date as long as the escalation runs between midnight and 5pm. Jenni Wacholz Remedy Administration Coventry Health Care Inc 480-445-2517 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dan Caissie Sent: Monday, April 30, 2007 6:47 AM To: [email protected] Subject: timestamp question (set date and time) ** Good Monday morning everyone :-) I have an escalation that runs at 1AM and what I want it to do is set a field to 5 PM for the current day. 4/DATE/2007 5:00:00 PM right now I was doing $TIMESTAMP$ + (60 * (60 * 16)) but if the escalation is delayed at all it will push the timestamp past 5 PM. So is there better way of doing this I bet there is any help would be great. 6.3 Windows SQL Dan Caissie _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
