>>Hi Cathy,
>>
>>I recently moved are apps to VFP9 (SP1) and am running into the problem you documented on your website:
>>
>>Gotcha: Dangling Datasession Left After Running Report
>>If you run a report using a ReportListener from the FFC directory, and you're using a successor listener, and that report is run from a form with a private datasession, you end up with a dangling datasession after the report completes. If you keeping running reports in this manner, you keep building up more dangling datasessions. I don't think I have to tell you the consequences of a long day of running reports like this!
>>
>>Is this still an issue? Workarounds?
>>
>>Rick Hawkins
>>RVSS
>>(Met you at the FoxPro Users Group in Philadelphia...)
>
>Yes it's still an issue ... No I don't have a workaround for it. We do have code in our app to make sure we close any open DBCs before closing the form ... but that doesn't get rid of the dangling data session.

I just tried something (based of a thread on Foxite) which seems to have fixed this (?)

1. I saved the datasession of my form (which has the private datasession)
2. I switched to Datasession 1 before I create my listener objects and successors
3. I then switch back to the datasession I started with before I issue the REPORT command

The report runs, and there is no dangling datasession after I exit the form. If this is working (still testing this), I wonder if listeners have some sort of presence in or want to work in datasession 1, and get stuck when they are created in any other datasession...