>A VFP developer I know said that excessive use of private datasession (i.e. setting giving every form in the application it's own private datasession) will slow the application down and even cause memory leaks and crashes.


>Any one else have experience that either matches or contradicts this?
>
>Many private data sessions no windows problems?
>
>Many private data sessions, lots of windows problems?


Gar, my reservation app is based on Visual FoxExpress which uses a private DS for every open form. Because I dislike the time it takes to build a form I've arranged for forms to stay open after the user goes to another form. All of the main (non-modal) forms have the exact same size and position so only the current one is visible.

Typically, users will have between 2 and 10 forms open at a time.

It's still not snappy fast but it definitely faster than rebuilding the form every time it's needed. The app does not seem to slow down as more forms are opened. I'm not aware of any memory leaks. (Which I have become intensely aware of in Access 97 under Windows 98!)

I changed the CodeBook DoForm utility to always look for a form before instantiating it.

BTW, this is not at all confusing to the user because they always call up a form in the same way, either from a button on another form or from the menu. I've also given them a "BACK" button on the toolbar that takes them back to the previous form. (It stacks 10 deep.) They seem to like that a lot.

Peter Robinson