>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.
>
>I have not been able to recreate this -- but my application is nowhere near complete, and the sample dataset is currently small. (A full size sample database is due on Tuesday.)
>
>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?
>
>I wonder whether this programmer simply bumped against some of the easily worked around "don't use a table in the default data session with different attributes then you use in the private data session" problem or if there are real memory and resource problems with private data sessions?
>
>Thanks in advance for any comments.

If the tables aren't opened, VFP will open them in the private datasession. You can speed this up by opening all the tables when you first launch the app.