RE: DDS Screens To Java

And if I can add a bit of constructive advice, take a SMALL subset of your
application; say customer entry/update  Around a dozen programs or so.  Run
the subset through a conversion (manual or otherwise.)  This 'first time'
will give you the absolute worst case scenario for how hard it will be to
GUI-fy your applications.  Then do it again with a second subset about the
same size.  This is a much closer approximation to how long it'll take to do
the actual work.

Remember to go end-to-end: from conception to conversion to 'touch-up' to
deployment to a client actually using it in a production mode (no
QSECOFR/QPGMR!)  That will expose quite a few strengths/weaknesses of each
technique.

If you convert the same subset several ways you will also be able to more
quickly see how they _act_ when you use them.  You can even run them
side-by-side for performance and 'look and feel' comparisons.  All on your
own hardware with your own database.

  --buck