>No, you're right. I don't want to go back to 'monolithic' procedure files. I wanted to break it up as David suggested so that each class was a separate module (file). I'm not sure I understand the VB reference because in VB each class is a separate file (class module).

John;

It might just be my view of the world. I see a .prg as one file and if you want you can add as many procedures and functions as you wish to one .prg. With VB (Access also – ugh) you have one .prg like file where you place all your code.

There are advantages and disadvantages to anything. It is nice to have one “file” where you can find things and at the same time it can be a pain trying to find or figure out what is going on. It is all just perception.

As for myself I like seperate files. For classes, I have used visual and procedural classes and each approach has its ups and downs.

Tom