>We had to "kludge" the way the screens first started so that on slow machines, the "default" menu, screen size/colors and screen header woudln't come up, before our custom screens were written...

The concept a splash screen is in 5 so you won't have any problem avoiding those defaults.

>We had done it in 3.0, but required "bulky" code at times to meet our needs....if 5.0 improves on this, all the better...

It depends on what kind of system and power you need. If you want to take a screen as is and make it run on the net asap then you might want to use ISAPI.

>We found that if a developer had been workind in the IDE for like 4+ hours, building, recompiling, testing, that the win95 resources got lower and lower...<g> Under NT, the problem was not a problem, a NT would keep VFP in it place...What leaks in particular have you experienced so far?

About the same thing. It's true that NT is more robust. 5.5 in March is suppose to fix those problems definitely. We'll see. :)

>And, in your opinion, the jump to VFP 5.0 is well worth it? <g>

Yes, of course, lots of major bug fixes and improvments but may require some modifications in your framework here and there because of non compliant stuff in 5.