[AccessD] Refreshing open forms when something changes

It may seem inefficient to you, but it is the essence of loosely coupled
programming, Jim.  Tightly coupled code is more "efficent", but  requires a
lot more effort to maintain when anything changes.  I guess it's a matter of
where you want to put your effort, into building loosely coupled code or
maintaining tightly coupled code.

Charlotte Foust

On Wed, Jun 22, 2011 at 8:26 AM, Jim Dettman <jimdettman at verizon.net> wrote:

> John,
>
> <<Jim, you are getting waaaaayyyy too bogged down in micromanaging things.
> >>
>
>   I'm not sure what it is I'm micromanaging<g>; all I pointed out was that
> if you implemented a message class as you outlined in your first post, it
> would be inefficient.  That was, and I think you would have to agree given
> your responses since then, a legitimate point.  You and Drew came back and
> said there are ways around that.  Great.  But for some, it might not be
> obvious that there were or that it might even lead to a problem.  But all I
> did was raise a valid point.
>