|
As long as the idea was to use RPG skills to build thick client applications that extend legacy systems, I was ambivalent. I think there are better thick client development environments, but on the other hand it's a nice way to leverage your existing skill set. However, now that the message is clearly to move your iSeries systems to .NET, I am quite opposed to the entire concept. What I want to see is someone stand up and say, "Leave the back end on the iSeries, and use whatever front end you want." That's the REAL answer. Joe > From: Pete Hall > > It's still primarily a way to access the iSeries from a gui, although they > do have a tool for getting at SQL server data using the same interfaces. > They've been GA with the .NET version of AVR for close to 2 years. AVR > always was a Windows product, so it's really not much of a change. In > reality, I don't think they had any choice. It was either get on board or > junk their flagship product.
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.
midrange.com
