Thew most elegant way (and the most complex, too) is to use a
database-stored repository of your forms....

with IBO this will be very easy, though....
Have several base-forms for your different purposes and base-datamodules,
too.
As IBO-dataawares are not persistent, but the Datasets themselves hold all
you need in stringlists, stream these stringlists into the database.
Now you can load a forms description and create the form at runtime with
ease....
For the interface, you can use also a list of controls ot create and where
to position them.....this is the way, almost all customizeable big systems
are running.
Or use the TIB_SearchPanel....it is a bit basic for now, but expect some
nice enhancements really soon...

This is surely a lot of work, but you will be save and flexible with even
end-user-customization-possibilites without headaches.
When funtionality is needed, use some of the scripting-components (I think,
the DreamScripter is very good) or a plugin-interface for dll's for
that.....

Nick Josipovic
Corporate Market Intelligence

Phone: ++49 6227 762945

> -----Original Message-----
> From: Leos Urban [mailto:leos.urban@...]
> Sent: Freitag, 19. Januar 2001 08:15
> To: IBObjects@egroups.com
> Subject: [IBO] Many applications and one connection
>
>
> Hello all,
>
> we want to create application system with many (>70) application.
> Applications (in this meaning) are function units (not executable!)
> as are editable forms (invoice, order,...), reports, cash views etc.
> Every function unit has one or more forms and datamodule.
> I prefer one connection to Interbase per user,
> user can run more application unit at the same time,
> every with own transaction.
>
> Solution:
> I plan one exe with one IB_connection (and menus)
> and all other units in BPL packages or DLLs.
>
> I don't know if this solution is possible and if does not
> exist better way.
> Do you have some experience with this solution? Any comment?
>
> Thanks.
> Leos
>
> PS: sorry if my English is incorrect.
>
>
>
>