This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C238A2.D855BC30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am with a company located in the Washington DC metro area that is considering migrating our HP-e3000 quick code to Axiant. We have a = large application with about 1500 Quick screens, 500 of which are relatively complex (from 1000 - 6000 lines of code). One idea we are considering = is migrating our screens to Axiant to provide our clients with a GUI = interface in the short term (next 1-3 years), and then initiating a brand new development project with a newer tool that provides a more robust = toolset. Another alternative we have been considering is scrapping the Axiant = plan altogether and initiating the new development project immediately, = using Java with Jdeveloper, and using a very methodical phased approach so we = can avoid the pitfalls of trying to convert a large system all in one bite. = We have already committed to Oracle for our database solution and are now = an Oracle development partner, so this might be a low cost alternative for = us. We have been prototyping Axiant 3.1 running against HP-UX server and = Oracle database for a few months now and have found a lot of roadblocks that = have been very frustrating for us. We have also been disappointed with the limited features of Axiant vis-=E0-vis a more fully object-oriented development tool. We are going to install Axiant beta 3.4 in the near future and do some further prototyping, but as with most projects these days, we need to make a decision very soon, so we need to get informed = as quickly as we can. My question is: Do any of you work at an Axiant development shop that = is also running Axiant in production? What I really need is to be able to visit a couple of development shops that have in-house developers, have implemented Axiant and will give me an honest evaluation of the issues = you have confronted during your migration/development effort. We really = need to know if our migration to Axiant is worthwhile for this relatively = short-term goal, how severe the issues are that we have found, and what sort of workarounds you may have discovered through your own experiences. = Ideally, we'd like to find someone close enough to our location that we could = visit in a day, but I'd really appreciate any feedback any of you might have = for me. We would really appreciate the opportunity to come and pay you a = visit. Please feel free to contact me directly at my e-mail address, which is listed below, or via the listserver. Thanks! > Jim Pantos=20 > Sr. Technical Development Advisor=20 > AMISYS LLC. > Phone: 301-315-7211 > Email: Jim.Pantos@amisysllc.com >=20 > Confidentiality Notice: This email message, including any = attachments, is > for the sole use of the intended recipient and may contain = confidential > and privileged information. Any unauthorized review, use, disclosure = or > distribution is prohibited. If you are not the intended recipient, = please > contact the sender by reply e-mail and destroy all copies of the = original > message >=20 >=20 ------_=_NextPart_001_01C238A2.D855BC30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">Axiant experiences I am with a company located in the = Washington DC metro area that is considering migrating our HP-e3000 = quick code to Axiant. We have a large application with about 1500 = Quick screens, 500 of which are relatively complex (from 1000 - 6000 = lines of code). One idea we are considering is migrating our = screens to Axiant to provide our clients with a GUI interface in the = short term (next 1-3 years), and then initiating a brand new = development project with a newer tool that provides a more robust = toolset. Another alternative we have been considering is = scrapping the Axiant plan altogether and initiating the new development = project immediately, using Java with Jdeveloper, and using a very = methodical phased approach so we can avoid the pitfalls of trying to = convert a large system all in one bite. We have already committed = to Oracle for our database solution and are now an Oracle development = partner, so this might be a low cost alternative for us. We have = been prototyping Axiant 3.1 running against HP-UX server and Oracle = database for a few months now and have found a lot of roadblocks that = have been very frustrating for us. We have also been disappointed = with the limited features of Axiant vis-=E0-vis a more fully = object-oriented development tool. We are going to install Axiant = beta 3.4 in the near future and do some further prototyping, but as = with most projects these days, we need to make a decision very soon, so = we need to get informed as quickly as we can.
My question is: Do any of you work at = an Axiant development shop that is also running Axiant in = production? What I really need is to be able to visit a couple of = development shops that have in-house developers, have implemented = Axiant and will give me an honest evaluation of the issues you = have confronted during your migration/development effort. We = really need to know if our migration to Axiant is worthwhile for this = relatively short-term goal, how severe the issues are that we have = found, and what sort of workarounds you may have discovered through = your own experiences. Ideally, we'd like to find someone close = enough to our location that we could visit in a day, but I'd really = appreciate any feedback any of you might have for me. We would = really appreciate the opportunity to come and pay you a = visit.
Please feel free to contact me = directly at my e-mail address, which is listed below, or via the = listserver.
Thanks!
Jim Pantos =
Sr. = Technical Development Advisor
AMISYS = LLC.
Phone: = 301-315-7211
Email: = Jim.Pantos@amisysllc.comConfidentiality Notice: This email message, including any = attachments, is for the sole use of the intended recipient and may = contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. If you are not = the intended recipient, please contact the sender by reply e-mail and = destroy all copies of the original message
------_=_NextPart_001_01C238A2.D855BC30--