[AccessD] Refreshing open forms when something changes

Jim, 

Just a word of warning... I completely agree with JWC on this.  If JWC
and I agree on something.... well, you can take it to the bank that if
you disagree, you'll end up having egg on your face! ;)

Drew


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, June 22, 2011 11:54 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Refreshing open forms when something changes

Jim,

 >    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.

To be honest I do not think it is inefficient at all.  It would be
inefficient if it made any damned 
difference at all.  It doesn't.  It would be inefficient if it were
sucking up processor cycles.  It 
isn't.  Is it the absolutely most efficient method of accomplishing the
objective?  No, but it makes 
no damned difference.  If I were to re-engineer it to be as efficient as
possible I would save 1 
trillionth of a percent of whatever metric you choose.
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.