Splitting code for a Class across multiple modules?

I have written code for Choicer, which is a Class Module. Broadly, the Choicer does two big things: it constructs a bunch of tables, and it puts Validation drop-down menus into cells. There's a lot of code in the module; it's getting hard for me to navigate. I'd like to split the module into two modules.

For a regular module, this would be no problem. For a class module, how do I do it? I don't want to create two different classes; I want to spread the code for a single class across two files.

If VBA had inheritance, I'd code two separate classes and let Choicer inherit both of them. Is there a comparable approach in VBA?

Andy, thanks. But Choicer holds a large number of parameters, and both the menu construction and the table construction use these parameters a lot. If I split the code as you suggest, then I have to pass the Choicer instance as an Arg to each method, and then code like

Please Login or Register  to view this content.

gets real cluttered with

Please Login or Register  to view this content.

which is what I was trying to avoid. So that means a lot of refactoring and then putting up with uglified code.

I appreciate you letting me know that what I want to do isn't worth the trouble in VBA.