↧
From: | Tuvia Vinitsky |
To: | Thierry Nivelet (FoxInCloud) |
Currently supported:
- DO FORM: adaptation is automated in visual methods, either .prg or .?cx
Next 2 versions to be released within 2 months:
- support for public variables
- support for _screen.properties
- support for menus, either thru .mnx or code
- listbox and combobox: support for additional .rowSourceType: 1 Value, 2 Table alias, 3 SQL statement, 4 Query (.qpr) file
Dear James,
The first thing to do is download from the FiC website the FAA application. The purpose of this application is to run it and let it go thru your VFP project. It will find anything that needs to be changed to enable FiC to work; it will also give you warnings abhout potential points of conflict.
My personal experience is that the amount of time and work estimated by FAA is higher than really needed. I also feel, although admittedly as a FiC consultant I am biased, that it is worthwhile after running the FAA to have somebody with FiC experience review the results and give you an idea of the size job involved.
From your description, if you have a lot of loose prg's that display visual VFP controls in the prg you will need to make those prg's methods of a form or class. Public variables similarly need to be changed to class, form, user, or session based variables.
Standard VFP classes and forms are easily converted by FiC with only a couple minor syntax changes, most notable a change to the DO FORM syntax.
Please let me know if I can be of any help. Good luck!
Tuvia