Mark, this is a special case which I've found very useful - the modal form 'defaults' to the private DS of the calling form. You are ALWAYS using a private DS, you just get to choose WHICH DS. It took me a while to get the hang of it, but I use it frequently now.

Barbara

>>PMFJI, but have you tried setting the modal form to 'default datasession'? This tells it to use the datasession of the calling form, (not the 'real' default datasession) and may solve your problem.
>
>Up until now, I have done all my VFP work with default datasessions. Now
>I'm experimenting with keeping all my forms completely independent of
>one another, and I like the results, mainly.
>
>One problem I found with using default data sessions in the kind of
>scenario I mentioned is if the second form uses base tables in
>buffered mode. When you start the first form (with the view), these
>tables are unbuffered; on return, walla, they're buffered. This caused
>update conflicts up the wazoo, although I found a good solution.
>
>Anyway, the long and short of it is that the problem is "fixed" simply
>by closing the base table before the requery on return from the second
>form. I'm not happy, but at least I get to keep using private DSs. :)