LJ, I don't disagree...I am just saying that using that function of archig may still pose a risk, since it is probably not used often, even though it seems a small risk. But if I ever had to change the table ID, I would use the archig utility, I would not do the manual updates at all.....
Susan: Yet another option is to create a database view with the schemaid you would like,provided of course there is no tabeld with that ID. So for instance let's sat you have table T500 and you would like T300, check whether there is a table T300, and if not, create a daatbase view caleld T300 that referes to table T500. This way, you don't need to change anything on the Remedy structures. Guillaume ________________________________ On Wed, Jul 28, 2010 at 11:15 AM, LJ LongWing <lj.longw...@gmail.com<mailto:lj.longw...@gmail.com>> wrote: ** That is always a chance…but I would trust archgid more than I would trust me doing it manually….and I agree with your assessment, TID should NEVER be used in direct SQL….I ALWAYS recommend using View names instead of table ids….still fragile, but less so that table id :) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
