|
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] The company where I am currently working is performing an evaluation of Seagull Software's Transidiom product as a means for integrating AS/400 data into a custom client-server order entry system. They are also considering using it for entering data through the AS/400 screens. I really don't want any commentary on WHY they are considering this, because I am trying to get them to consider OTHER ways of doing this, such as using ADO/OLE DB or even ODBC. I have a preconception that there could be major problems using this technology. However, I think that they are Hell-bent on doing it this way and I need some empirical evidence to help make recommendations. So, 1) Is anybody using this software or anything like it (JWalk, etc)? 2) If so, what kinds of major issues (if any) have you encountered while using it? 3) Has program change management been difficult when using the screen-scraping product? 4) Since the screen-scraping scripts have to be changed (or at least tested) every time that any screen or program changes are made on the AS/400 side, how much time has been added to the system development cycle? 5) Any gotchas? Thanks for your consideration....
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.