>This is my first time with 2.6 (Geez!) and I'm not really liking it. :)

>Now, when converting those screens to 5.0, the converter adds a pageframe and a formset to the screens. Of course I want to get rid of those (Where talking 1K+ screens here). There goes Alex, browsing everything he could, until he found an article in the help file ("Changing Converted Screens to Visual FoxPro Forms").

>Of course, poor me, it didn't solve my problem. When I try to run the royal pickyness, I still got those horrible "Variable not found. Unbinding object...".

>Is there any charitable soul in this world that can tell me what's going on and, if at all possible (buy you a beer. If you don't like beer, no problem, I'll drink it myself) how to solve it.

>Thanks heaps.

>Alex, freezing.

i am working on a 2.6 to 5.0 conversion. new to 2.6 and 5.0. can say that 5.0 is much superior to 2.6. however, that is the only good news. our application is a complex real estate lending applilcation. It has about 17 primary screens, about 50 modal screens, reporting, query maker, upload, download, and several interfaces. not a small application (by my standards). the 2.6 is has been working in the field for over 4 years. it is very stable and relativly bug free. The 5.0 conversion has three people working full time for now over 6 monthes. And we only converted the 17 main screesn. the 50 modal are still 2.6 converted (windowtype property of 3 or 4).

Several of our most time consuming issues.
1. we converted browse windows to grids. do not do this unless your browse windows are extrememly simple, you have lots of time, or you want to start heavy drinking while you code.
2. decided to use a toolbar instead of buttons on the form. toolbar does not take focus, which caused the last control not to fire its valid. real problem if you have a save button and the last control has not been validated. this was a big workaround for a non 5.0 person.
3. changed to a sdi (toplevelform) instead of using the vfp form (_screen). the toplevelform has several nuances and bugs.
4. rewrote the 17 main screens because we were not able to edit grids or have more than 2 pages on a pageframe for windowtype of 3 or 4 (2.6 converted windowtype property). we could have more than 2 pages, but when a modal form took focus and then the page received focus again, it reverted back to 2 pages. weird things with grids and pageframes in 2.6 converted (windowtype 3 or 4) 5.0 forms.

about removing the formset and pageframe. you will not be able to compile correctly unless you change the windowtype to a 1 or 2. we tried to remove the excess containers, and got compile errors. seems the 2.6 converted forms require the formsets and pageframes.

wish we have given all our free tables unique indexes and moved them into databases. free tables with no unique indexes have many limitations with updating from views.

may the force be with you - brenda