[AccessD] A2003:Replacing 'tokens' in a string

A hammer?  Really?  You really should get more familiar with classes.
The example I posted also only took 2 minutes.  It wasn't completely
generic.  I could have added the ability to make the delimiters and
wrappers variable.  But what I did put in provided a listable display of
data and key names, and made retrieving any single value, by keyname
beyond simple!

Really Max, go look at my example.  Other then saving one part as a
class, and then adding the data to a collection (other than keeping it
in an array), my example is pretty much identical to yours.  So the
extra time involved....hmmmmmm, opening and saving a class.....another
line or two of code.... for the flexibility AND READABILTIY, that was a
few seconds well spent.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Thursday, January 28, 2010 6:54 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2003:Replacing 'tokens' in a string

My lazy code took 2 mins.
I didnt mind doing it because it was for somebody else - therefore 2
mins well spent.
If I was doing it for myself I would have paramatised it.
Familiarity with classes, like other thinks, does bring its own reward
in terms of speed and efficiency - agree with you there.
I dont agree that you need a hammer aka class to solve every programming
task.

max


On 28/01/2010, jwcolby <jwcolby at colbyconsulting.com> wrote:
>  > Yes John/Drew but why use that horrendous code when you can do the
same
> with this..
>
> The answer of course is that horrendous code is only horrendous code
if you
> can't knock it out in 2
> minutes.  It takes me about 5 minutes longer to do a generic solution
that
> can handle this same
> requirement than it takes you to do the one liner that only handles
this one
> specific solution.
>
> Why?  Because I am comfortable with classes.

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.