I don't understand why you're using datasessions like that...

This is how I use data sessions:

1. Only report printing utilties use the default datasession
2. Every independent form/formset uses it's own private datasession.
3. The only time I use a datasession from another form is in dependent, modal forms. (i.e. the the senior form can't be closed without the dependent form being closed.
4. If I need to keep pointer locations consistent between forms, then I log the current primary key(s) from the parent table(s) as property(s) of the main application object and then put a seek in the activate method.

Although I like the counter idea proposed in another response, I think that your situation requires that each form use it's own private datasession. (I'd also defer to Arnon's suggestion to use the session object, although I haven't used it yet).

HTH