Hi Phillip ---

OK --- lets look at it another way. You could, in your core app, have a very basic Form class. In your DLL, you could store scripts for creating a form by using AddObject reading the script and maybe metadata. Business rules would be stored in a metadata or business objects coupled to the DLL or ActiveX EXE.

I think it's doable but a serious pain inn the ass :-)

The perl analogy is lost on me :-) Haven't even looked at UNIX since the AT&T 3B2 and then I just looked at it and ran to the bathroom to throw up.


>John -
>
>I'm hoping to avoid DLL's as much as possible for just that reason. The UI is going to vary quite wildly from module to module, without a doubt. And to integrate all UIs, which I don't even know what they will all look like, into the core interpretation database, would be instant bloat the likes of which none of us have ever seen before. (You thought 250M for one app, sans docs, was bloat? Wait'll you see THAT mess.;)
>
>What I'm hoping to do is something similar to perl, or sort of, for lack of a better example. Basically, the modules are standard VisFoxPro forms, with non-standard programs that are interpreted by the moduleInterpreter code.
>
>Prepare for bloat, or start hacking now? ;) Thanks! :)