Hi Barry:

I did a lot of FPW2.6 application porting into VFP and used Codemine -- www.codemine.com . Whilst there is nothing specific in the framework to this task (like Wizards), it is very easy to specify and use Foxpro 2.x tables. Also, within the Codemine DataManager (DM) and Codemine DataEnvironment (CDE) classes, it is likewise easy to specify referential integrity (RI) rules without the need to use the VFP database container (DBC). From your perspective, this negates the need to alter your table formats from 2.X format to VFP whilst developing for VFP. Also, whilst local views could be used to access Fox 2.0 data, this can be a bit of a hassle when you can simply use the Fox 2.0 table in exactly the same CDE as VFP "free" tables, VFP (dbc-connected) tables, Local Views, Remote Views, ADO and some framework speciality SPT type cursors. So, if you want to share your Fox 2.x data with your 2.6 applications at the same time as you are developing your VFP version, this becomes a no-brainer. You can also specify in the Codemine DM and CDE what you logically designate as Primary Keys even though Foxpro 2.x tables have no capability to designate a primary or candidate key (you can designate candidate keys in VFP "free tables"). So, from a concurrency of development perspective, Codemine is a good fit.

HTH

>I am looking to purchase an application framework to update and re-engineer my entire collection of Foxpro for Windows 2.6 applications to VFP 8.0.
>
>Does anyone have any suggestions as to which ones would be easiest to use since I consider myself a very experienced FPW 2.6 developer, but a newbee to VFP.
>
>Barry Kucher