>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).

Yes, more or less the same here. Except that "someone" (aka "The Boss") didn't want anything to be changed. You know the style: Just recompile it and it should be faster because it's a newer compiler. This was 4 months ago. Now he hired me to clean up the mess but still doesn't want much to be changed because they already spent too much time "converting" it. How does one deal with someone like this? Yup, my opinion too. I'll go have a beer. :-)

Before that, I suggested training the development team (nobody knows zilch about VFP or even something more simple: "What is an event"!). The VP suggested changing the whole team, but for humanitarian reasons, I can't agree with that.

>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.

Coffee you mean? :-)
Once you set an appearance to what you want, templates work well. For me, at least.

>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.

That's one of our problems. We have to keep the feature-wealthiness to a minimum. Our software is a POS, to be used by people who don't know how to turn a computer on. Mouse is out of the question.
Excuse me: Jeeeeez!

>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.

Yes, this is a real pain in the you-know-what. Blaaarrghhh! I hate those READ's.

>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.

I did some tests with it. Apparently, the process is simple. But that depends on the application. In my case, there's so much spaghetti underneath that if I eated it all, I wouldn't have to cook for a year or two.
The whole concept changes. And the current problem (I refuse to call it program) is designed to be working with those tricky READ's. Yuck.

>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.

Ah yes. I've put that in my wish-list. I'll try to convice the man to do it while we're at it.

>may the force be with you - brenda

Thanks. It's hard to fight the dark side.

Alex, slave to work