Hi Jim!

>Changing data sessions can be a dangerous thing to do if you do not restore the data session properly. A better design might be to build your Methods class to be a light weight object and then in your form class put one them in the form. Then make your calls THISFORM.oMethods.SetSets().

Perfect! As always a great answer! It's working like a charm now. We just added the Methods class to our form and we call the methods. This way they are in the correct datasession without any hassles.

However: we are in a discussion here. One party wants to switch to a procedure file altogether. So dump the oMethod class and use one big procedure file with all the procedures which are in the oMethod class.

And another party (me :-)) wants to keep the current way of working. So use the oMethod class as a subclass of the Formclass.

We would like your opinion about this matter. What would be better? We know both ways work perfect. But what is good programming? Or is it just a matter of taste?

Thanks for your time!