Using ROWID (if that pseudo column is what you meant) from that table is longer than 15 characters anyway.. If I am not mistaken it is 18 characters.. ROWNUM would be more your solution than ROWID.. Why would using ROWNUM not be appropriate? The RequestID field is just for the purpose of building your view form. You can keep your GUID field that you get from that table as another unique ID, which you could use for identifying your record instead of the Request ID.. Use the Request Id only for the purpose of respecting what ARS needs to create your view form.. Joe
----- Original Message ---- From: "Moore, Christopher Allen" <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, August 20, 2008 3:53:42 PM Subject: Another view form question... ** I have a problem creating a view form- thanks to Joe’s advice I am now able to see all the columns. My problem now is designating a key field. The only column which is guaranteed to be unique is a GUID passed from the external data source, but it’s too long- 25 characters. Has anyone else run into this problem, and how did you get around it? I can’t use ROW_ID because this table will be overwritten monthly. I know just enough SQL to be dangerous…is there some sort of way to add a column and ensure it’s unique via SQL? ITSM 7.0.1 p6 SQL 2005 SP2 Win 2003 svr I appreciate any advice! Chris _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
