|
>> You need to have authority to read/write the registry for most of the old CODE/400 tooling I believe. We were aware of that issue Mike - although it is only the Hosts file I have had problems with - WDSc wants to create an R0.. server name when you launch from within RSE. If you just run CODE or Designer stand-alone it is not an issue. This one was simply perverse. I suspect that maybe the old CODE parsers for DDS are being used "under the covers" and that's where the limit comes in. My complaint is twofold. First of all if there is a limitation it should be checked for and handled. Under no circumstances should opening a source member cause the entire workbench to crash. Secondly - any checks should be made when user loads the product for use. If WDSc _requires_ to be run by a Power User it should ***** well check for that when loading! Mike, I'm sorry if this sounds harsh, I know you guys bust a gut to give us the maximum features with the resources you have. Fact is though that we just wasted hours of our own time and hours of several customer staff because of this. Some of those staff were the died in the wool "old school" programmers that IBM is so keen to convert. Guess what they thought of the "new fangled tools"? The product had been loaded, patched and tested. Having it suddenly start blowing up in the middle of the class was just not acceptable. Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.