Dragan and Scott, thank you very much.
The first version will have all its code in one place - prg.
All the best
Kamil

>
>You're trying to store your metadata (formulas) in an Excel sheet? In a comment field that you don't see until you hover your mouse over it (but then so can the users see it) and can't touch unless you rightclick the cell (but then so can the users - or you'll have to write some serious VBA code to stop them)? What happens when your code-in-excel-comment requires something you haven't foreseen? You'll have to write more code again in your main app to provide it. Code is code is code, and your attempt to answer The Question Of OOP ("where does the code go?") is among the more complicated ones.
>
>Why not keep your metadata in a table - scripts and formulas and whatnot? Just three fields - (row I, col I, formula M) would be a start. If the coordinates of your formulas are variable, well, then, store their address (name of a named range, or the code which calculates the location) in a location memo.
>
>That way you don't have to rebuild your app - but...what Scott said - I concur. You keep your code in memo fields, in a separate file. But then, a .prg is also a file, and far more readable than that in memo fields (and you get the syntax checking, intellisense etc), and, besides, rebuilding an app isn't such a big deal nowadays. It's just a few seconds. I know my machine creates a 22M exe in about six seconds or less.
>
>IOW,
>- yes it can be done your way but I expect it to become complicated and/or potentially unstable
>- yes it doesn't have to be inside the app; there are ways (metadata tables, separate out-of-exe .prg files, even prg files generated and compiled from metadata on the spot - I do that sometimes)
>- still, no convincing reason why not to keep it inside the app.