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:[email protected] ARSlist: "Where the Answers Are"

Reply via email to