GS wrote:

Good reply! Wasn't thinking about adding to a VBA project...

In this case the entire module code could be written in a single
column, then exported to a .bas, then imported into a VBA project.

The page I linked to shows that exporting to a .bas is an unnecessary step.

IIRC it can also be done via the VBScript runtime using eval() -- but it
looks like that function may have been removed from Win7 (at least) because I
can't get it to work here, even in a .vbs file... and I don't really care
enough to continue investigating.

--
Unless you're driving a f%*%$)g battleship,
the train is ALWAYS going to win.