[AccessD] Find First in an Array? - The Solution Revisited - Now Tag is the Answer

jwcolby jwcolby at colbyconsulting.com
Tue Feb 24 15:34:54 CST 2009


 >No you don't; code for manipulating tags to store multiple values has been floating around since 
A2 and has been discussed numerous times on this list.

That is true Jim.  It is however almost exactly analogous to denormalizing a table by storing a ton 
of entirely unrelated data in a single field in a table.  Sure it can be done, but you won't catch 
me doing it (anymore).  The pluses just don't outweigh the minuses.  Put that same stuff in a table 
and load it from there as the form opens.  Once you load it you REALLY don't need to place it in a 
tag because you have much better constructs to use.

I am sure it used to make sense back when a computer was dog slow, only had 64 megs of memory, and 
had slow hard disks, slow networks and so forth.  To try and justify it now becomes a stretch.

John W. Colby
www.ColbyConsulting.com


Jim Dettman wrote:
> Drew,
> 
> <<Sorry to chime in here late...but if you use tags for a system wide
> process you completely eliminate the ability to use the tags on the fly
> for other purposes.  >>
> 
>   No you don't; code for manipulating tags to store multiple values has been
> floating around since A2 and has been discussed numerous times on this list.
> 
> Jim.
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Tuesday, February 24, 2009 2:27 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Find First in an Array? - The Solution Revisited -
> Now Tag is the Answer
> 
> Sorry to chime in here late...but if you use tags for a system wide
> process you completely eliminate the ability to use the tags on the fly
> for other purposes.  
> 
> 300k in memory is nothing nowadays.  If we were designing systems back
> in the 80's and 90's, sure, but in today's world, most cell phones have
> more computing power then a high end system in the early 90's.
> 
> I didn't read every detail in the 'tag' solution, but I believe it
> required saving the design of the forms.  Using a class solution (and
> using the Event driven method, so that translations can be changed by
> the user) prevents constantly having to redesign every form.  And leaves
> the tags available for other purposes.
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Monday, February 23, 2009 11:29 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Find First in an Array? - The Solution Revisited
> - Now Tag is the Answer
> 
> OK.  But the whole point of the tag goes away when you have a wrapper
> class.  The purpose of a tag 
> is to contain "anything" that the developer wants for that form.  Once I
> have a wrapper class I can 
> simply create new properties of the class, with strong typing, etc.
> 
> If you have a class you no longer need a tag, never mind a whole
> collection of them.
> 
> John W. Colby
> www.ColbyConsulting.com
> 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.
> 
> 



More information about the AccessD mailing list