Thanks for the advice, it's clear that IBO is optimised for a setup
like your, but I think that with little effort it could be very good
with mine too.
There could be a lot of discussion about pros/cons of datamodule.
I'm using a mix approach, since I've decided to put a "local"
transaction on each form. Queries, stored procedure, cursors,
datasources are on the datamodule, and I've multiple datamodules
divided by "meaning" (base queries, accounting ones, etc.). For
lookups tables, I use a generic approach setting a design time a query
for lookup (in the datamodule, of course), and writhing code in each
form that uses it for specific setups (KeySource, KeyLinks). This way
my code is highly centralized, redundancy is put to the minimum, etc..
The only problem is when, for particular needs, I want to intercept
some of the dataset events for a job specific to that form. For doing
this I would need a "DatasetSource" component as required in my post.
This way I think IBO can accommodate both "data module centric" and
"form centric" way of programming.
I would like someone to reply too to my previous messages about a
IB_UpdateWork bar and related, generic forms.
I think that IBO apps don't have to look all the same, since users,
tasks, level of complexities are different in the world, so IBO should
do it's best, especially when is a simple task like this, to
accomplish them.
One thing that I would like to see too is a special colour for the
current focused component like the colours for the ColorScheme
property. Often, especially when the user is often interrupted, is
very good have the entire focused control being identifiable, without
the need of look at the small, slim (ok, blinking ;) cursor.
What about this further idea?
Thanks
Marco Menardi

--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> Not everyone will agree but... Put the queries on your form. That's
what I
> do.
>
> DataModules are for things which are global. If something is
directly
> related to a form, put the queries and transactions, etc. right on
it.
>
> In my apps, forms are independent objects which I keep as self
contained as
> possible.
>
> FWIW,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Marco Menardi" <mmenaz@l...>
> To: <IBObjects@y...>
> Sent: Thursday, November 22, 2001 12:25 AM
> Subject: [IBO] Need to make forms "DatasetAware"
>
>
> > Since I'm extensively using data modules as container for my
queries
> > and datasources, but often I need specific control inside the form
of
> > the dataset behaviour, wouldn't be necessary a "source" component
to
> > make the form DatasetEvents aware? A sort of TransactioSource that
has
> > the same IB_Query events and that are triggered by the events of
the
> > linked dataset? (so the form can react to AfterInsert, AfterPost,
> > etc.).
> > Maybe is not too difficult to be made, but there must be a much
better
> > knowledge of IBO than mine...
> > What's your opinion? Any volunteer?
> > Thanks
> > Marco Menardi