>In my apps I sometimes notice that data sessions with open tables are left around after a form (and sometimes the app in dev mode) is exited. I assume that this is a bad practice.
>
>Any suggestions on a routine to call in a forms.destroy (or other method) which would handle the data session and any lingering object references?

Let's take just one example. I'd look into why they're being created, first. Are you using SESSION object? Or do you use SET DATASESSION TO in production code? Private DataSession forms, reports? Default? Mixture? If you can zero in on one example, that you can reliably duplicate, then we could offer some suggestions. Otherwise, we'll just be guessing. Not that that's ever stoppes us in the past, but it would help focus the replies.