K
KevinRyer
Guest
We have an internal delivery system that allows you to move programs to our customers on a ticket by ticket basis. So if you changed 10 programs under ticket 1234 and 15 programs under ticket 4567 the system is smart enough to allow to move all the programs at the same time without manually moving files. The system is smart enough to know that if you have some overlap on those 2 tickets you can't move 4567 unless you move 1234 at the same time. Recently we added the ability to test for CRC errors . So if you needed to apply a DF when you move a ticket, we can check the production system and make sure the tables match what the code is expecting. We are using the feature RCODE-INFO:TABLE-CRC-LIST (which is awesome by the way) to do this. The one problem we have is if you add an index and only an index, the system doesn't see that difference. I would like to request you add a similar feature for indexes so we can avoid hitting this problem at a live customer (like we did today) This is the message you encounter when it happens Unable to locate index 'indexname' on table 'tablename' for procedure 'sample.p'. (7967) Another customer apparently reported something similar in the support kbase http://knowledgebase.progress.com/articles/Article/Finding-out-indexes-used-by-r-code-without-running-the-rcode
Continue reading...
Continue reading...