>>>1. Does the finish executable still have to be kludged at start to not "look" like the VFP IDE? IE, does it flash "Visual Foxpro" on the application bar, ect?
>>I never had that bug with 3 or 5.
>
>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...

You can avoid all this at startup. 5.0 also handles forms MUCH better.


>
>>>2. How are the new client/server and remote network data source stuff working out? Anybody done any internet apps with it yet?
>>
>>You were able to do Internet app with 3 as well. It doesn't have to be Client/Server as well. But, if this is the case, you can use Cold Fusion. If not, you can use XWorks, FoxWeb or West Wind Connection. For Microsoft based products, you can use ISAPI. It works but not powerful.
>
>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 is going to depend on what your "bulky code" did.


>
>>>3. Have the memory leaks that occurred in VFP 3.0 been repaired?
>>
>>There's still a few in 5 but not as it was in 3.
>
>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... 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?

Memory leaks were fixed in 3.0b.

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


YES!!!!!!!!!!!!!!!!!!!! The improvement in the debugger alone makes it worth the upgrade.