John is right.
The contents of the 'Request ID' field do not mean what they used to.
It used to be that this was the primary key that would be used for gluing
records together and it was commonly passed to other records via macros
way back when. Starting with version four, a new function called GUID was
introduced. The GUID function generates a unique string each time that it
is called.
It wasn't too much longer after that function was introduced that new
development started using it to link records together. If you have any of
the OOB apps, you should be able to find a display only field on your
parent form that is labled something like 'instance id' or the like that
is used to contain this value (loaded via an active link).
Yes, it is certainly possible to reset the value for the Request ID at the
database level. No. I am not going to explain the process. It has far too
many pitfalls that one can run into, especially considering the things
that can crop up. It is an ugly process, unless, of course,
tsql/plsql/sql does not hold a whole lot of mystery.
One other thought: if you have any custom development, and the Request Id
was used as the 'glue' to link your parent and child records together
(which was often the case in the old days), then your update process would
have to update those columns as well. Now that could be probematic if you
missed one, in which case your referencial integrity would fall into
question.
On Wed, 6 Sep 2006,
John Sundberg wrote:
I think the number should be meaningless. In other words - I suggest leaving
the system as is.
Benefits:
free
fast
get to work on the next higher value project
etc...
-John
John David Sundberg
235 East 6th Street, Suite 400B
St. Paul, MN 55101
(651) 556-0930-work
(651) 247-6766-cell
(651) 695-8577-fax
[EMAIL PROTECTED]
On Sep 6, 2006, at 2:10 PM, Kathy Morris wrote:
**
Hi all,
Because some workflow had the wrong qualification from a previous developer,
15,000 tickets were generated. We left off at 7,000 and now we are at
22,000. Isn't there a way thru SQL to reset the value of the HPD to 7,000 so
Remedy goes to set the next ID, it will think the last ID is 7,000. We also
want to rename the HPD tickets created today with a 7,000 value within the
database.
Our case ID is C1, I can find out the t table, I am just not sure which
command I would enter to modify the rows in the database. And if this will
present problems later. I know the users will be referencing the wrong
ticket number. We definitely do not want to be at 22,000.
__20060125_______________________This posting was submitted with HTML in
it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
