Allan,
 AW> What tools exist in the newer Windows version to make "changing
 AW> horses midstream" worth considering??? (I chunked PdoxWin v1.0,
 AW> but they must've done something by V5.0, no?)
At this point, the only real migration tools are the Object Coverters, which 
take a PXD form and generate a PFW form that has a similar look.  However, 
this may not be as bad as it sounds.  After all, PFW does away with a lot of 
the most annoying limitations in PXD.  For example, a 1->M->M form in PXD 
requires a lot of code to manage well, but in PFW, this is a snap and takes 
no code.
 
Additionally, the underlying architecture of the two products is different 
enough to make conversion tools very difficult.  For example, PAL is very 
tied to the menus of PXD.  ObjectPAL, OTOH, is separated from the PFW UI.  
PFWdoesn't force you to be aware of the current image or Desktop state.  
Everything can be self contained.  Thus, you can add a button to a form that 
makes some wholesale edits to a table that's displayed elsewhere.  Not saying 
this couldn't be done in PAL, just that it's a heckuva lot easier in PFW.
 
Naturally, there have been some changes to the product since 1.0; it's fater, 
easier to use, stabler, and so forth.  But, it still takes some work to 
create a Windows variant of your PXD applications.
 
(BTW, I often recommend that folks migrating from DOS to Windows use the DOS 
product as much as possible during the transition.  In Windows 3.1, this is
an interesting and effective way to buy yourself time to make the transition 
while still supporting your customers.)
 
Hope this helps...
 
-- Lance  
--- Maximus 2.02
---------------