>How bad is to have an application with lots of forms with private sessions?
>
>I am having some trouble with my application and I am getting sick debbuging it so I thought I could just leave the forms I have problems with, with the Datasession set to Private and debbug them with more time. (I have a deadline and basically that's the problem).

Generally it is healthier to use private datasessions for modeless forms, and default ones for modal forms called from them (i.e. if you want to synchronize content, stay on the same records etc, and the modal form doesn't try to reopen the tables which are already open).

You'd generally have less headache with private datasessions, for several reasons:
- no worries with wich tables to close and which not when you release the form, they all close
- no collisions with multiple open forms using the same tables
- you can open the same form many times and edit different records. Can't do that with the default datasession unless you keep inventing new aliases, which would need a lot of coding if your controls are bound.