That's usually the way the "you have uncommitted changes" message pops up, isn't it? I could see how that would orphan one if you didn't handle errors properly in an EXE. All my fun was in the DE.

I originally thought one of my views was failing so I tried error trapping - nothing failed. Running with a SET STEP ON in the Error method of the data environment did nothing. Closing the tables in the Unload, did nothing - the "unknown" data session was still there with nothing at all open in it.

That's when I noticed that there is no way to clear it <g>

I guess I'll just have to start a wiki topic on it. I'll do a bit more research first and see how many ways I can orphan one. Hopefully, it'll save someone else a few hours of "hugh? what the..."

Thanks!