No problem.. and use ROWNUM and not ROWID.. ROWNUM starts with 1 and increments by 1 so you are very unlikely to hit the 15 character limit. ROWNUM like the ROWID is also a pseudo column and you will not need to do anything else to set a value to it - its already there once a row is created.. either in a table or a view or in the results of a select statement as below.. Look at the example below.. SQL> select rownum||' '||table_name from all_Tables where owner = 'ARADMIN' and table_name like 'F%'; 1 FT_PENDING 2 FILTER_SQL 3 FILTER_SET 4 FILTER_PUSH 5 FILTER_PROCESS 6 FILTER_NOTIFY_IDS 7 FILTER_NOTIFY 8 FILTER_MESSAGE 9 FILTER_MAPPING 10 FILTER_LOG 11 FILTER_GOTOACTION 12 FILTER_GOTO 13 FILTER_EXIT 14 FILTER_CALL 15 FILTER 16 FIELD_VIEW 17 FIELD_TABLE 18 FIELD_REAL 19 FIELD_PERMISSIONS 20 FIELD_INT 21 FIELD_ENUM_VALUES 22 FIELD_ENUM 23 FIELD_DISPPROP 24 FIELD_DISPLAY 25 FIELD_DIARY 26 FIELD_DEC 27 FIELD_DATE 28 FIELD_CURR 29 FIELD_COLUMN 30 FIELD_CHAR 31 FIELD_ATTACH 32 FIELD 32 rows selected.
Joe ----- Original Message ---- From: "Moore, Christopher Allen" <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, August 20, 2008 4:22:35 PM Subject: Re: Another view form question... ** Good point- once we get the data from our view into out regular form we don’t care if the ID is being re-used. Thanks again Joe! ________________________________ From:Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Wednesday, August 20, 2008 3:20 PM To: [email protected] Subject: Re: Another view form question... 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"
