@Matt, I'm probably going to build a Dialog that lets them select the date they need, store it as a DATE field for workflow and display YYYMMDD (at the request of the user).
My RFE will probably be to get the same interface for DATE fields (calendar widget) with the ability to type in any year value. @Mark, Yes I will be doing those types of error trapping. Thanks, --- John J. Reiser Senior Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Carey Matthew Black Sent: Wednesday, December 23, 2009 9:14 AM To: arslist@ARSLIST.ORG Subject: Re: Epoch time rollover issue for dates past 2037 John, Given all that you said.... I would suggest that you do all of the following: 1) Use a UI that you build ( if you do not like the default UI ) A display only dialog, called from a custom button and suppress the OOB UI for the field. If you have to ... go all the way to a DVF for a custom "Web'ish" UI. 2) Use either a Date field or a Char field ( up to you ) to hold the data. My two cents... use a Date field. It makes doing math much easier than using strings. 3) Submit an RFE for what you want the product to do (or not do). HTH. -- Carey Matthew Black BMC Remedy AR System Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Tue, Dec 22, 2009 at 3:23 PM, Reiser, John J <john.j.rei...@lmco.com> wrote: > ** > > Hello Listers, > > ARS 7.1 Patch 004 > > MS SQL 2005 > > > > We have a need to record an end date greater than 2037 and the Date/Time > fields are restricted by the 32 bit integer of Epoch Time. > > I prefer to avoid Date only fields because of the widget and the BC check > box. > > Do Date only fields cause any workflow headaches? I will probably need to > check End Dates against the current date when records are entered and > retrieved. > > Example. Don't let a date be set in the past. Lock out changes to a record > if the End Date has passed when the record is opened. Etc. > > Just looking for a sanity check. Is there a better work around like > formatting the date to a character field (YYYYMMDD) or do I just use the > Date only because "it's fully supported by BMC and it was designed to > address this type of issue." > > > > Merry Christmas to all. > > Thanks, > > --- > John J. Reiser > Senior Software Development Analyst > Remedy Administrator/Developer > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
