Hi Jacob ----

What I have found is, if the original source uses standard notation (like g for global variables, et al), you can refactor the original from using memvars and procedure files to Custom object properties and methods. While you're refactoring, try to create Custom objects that are logical groupings of services or related activities. Within the code, what was:

SET PROCEDURE TO finfuncs  && Financial functions
PUBLIC gnSaleAmt
PRIVATE nCommAmt
gnSaleAmt=100.00
nCommAmt=CalcComm(gnSaleAmt)  && Calccomm is a proc in finfuncs

---is now----

SET CLASSLIB TO myclasslib
LOCAL nCommAmt
oFinFuncs=CREATEOBJECT("finfuncs")   && The Custom class
oFinFuncs.nSaleAmt = 100.00          && A property of the class
nCommAmt=oFinFuncs.CalcComm(oFinFuncs.nSaleAmt)  && A method in the Custom 

This should get you throught the initial conversion. Afterword, you can further recode to take further advantage of the VFP environment.

>I currently have a large Procedural Vertical Application written in FPD26. I want to give it the look of Visual Forms without necessarily converting my procedural code. I know that I can embed DO FORM statements in my current code which should produce screens that look like VFP screens, yet I have been told that it will not work properly. I have also been told that I cannot do anything within Visual that will allow me to use my procedural code and build a and compile a project under Visual using my existing code to any extent.
>
>I find this hard to believe that Visual does not allow for the use of procedural code.
>
>By the way... I know that OOP etc. is the way to build a new app. I also know that I am not prepared to trash years of work on the alter of OOP. I need an approach that will buy me the time I need to rebuild my code. The look of Windows will do that. BUt I want it to be handled from within VFP..
>
>Can anyone help. All advice will be seriously considered.