Steven, I would strongly suggest that you NOT alter the field 1 value. Add a new field. Do your business logic there and then propagate those changes to the table fields/forms of interest too. Simply add the time/cost of all of those changes and inform your management of the impact to the application and any future upgrades. See how much they think this is really worth.
Generally I find that when you can use existing functionality (AKA: 'Create Date') and not have to do additional, expensive, and difficult to maintain "enhancements" appeals to most management types. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 4/20/07, Steven Pataray <[EMAIL PROTECTED]> wrote:
** My managment would like to have a date included our HelpDesk Case number i.e. HD20070420xxxxx. The xxxxx would be the actual sequential case number. They would use this so they know what day a ticket was created. I really don't want to create another field with this number appended to each other since a lot of the reports and table queries are based on the Case number. Does anyone have any advise how I can achieve this? Thanks Steve ARS/HelpDesk 6.3 patch 19 Oracle 10g R1 Clustered Application server Windows 2003
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
