[AccessD] Sending a Text Message From Access

Thanks for your comments, Gustav.

Funny that you don't see my sender name in your mail client.

No, I am not a VB man.  And yes, I know how to write text files directly.

Having said that, I freely admit that in this particular context, I really 
do use code along the lines of that shown.

In fact, I have a personal preference for using a lot of db.Execute strSQL 
in my code, where others might do otherwise.  I just find it easy to work 
with, and that's my main reason.  As far as I am aware, from a performance 
point of view (in the case of appends, updates, and deletes), this is more 
efficient than looping through recordsets - but then I have never really 
worried about a few milliseconds between friends.

However, in this example, most (though significantly not all) of the appends 
are only adding one row, so I admit that this seems awkward.

In Wellington, where I live, it can sometimes rain on Saturdays during the 
winter.  Stuart will testify that this is a very unusual occurence.  But 
when it does happen, the users are often sending hundreds of text messages 
with one click, and in practice they go in the blink of an eye, so I'm happy 
with that.

Nevertheless, you have prompted me to think about it again, and I certainly 
see your point that there may be neater options.

Thanks.

Regards
Steve


--------------------------------------------------
From: "Gustav Brock" <Gustav at cactus.dk>
Sent: Saturday, August 08, 2009 10:43 AM
To: <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Sending a Text Message From Access

> Hi Steve
>
> My apologies. No one here deserves to be mentioned in third person. I 
> didn't read the name of the author, and even when I did now, I didn't know 
> at first it was you because my mailer only displays miscellany at mvps.org as 
> the sender of your messages and, as I was convinced mvps presented 
> themselves by real names, I have always believed your name to be Steve 
> Miscellany. Well, laugh, but these days people can have the strangest 
> names.
>
> But - speaking freely - after a real life experience rewriting code with 
> endless series of db.Execute and SQL commands for everything written by a 
> hardcore VB programmer obviously not aware of the power of DAO (and thus 
> missing a 20 fold or so speed increase), I've since then used this coding 
> style to separate VB programmers from real Access programmers who are 
> raised with DAO (or ADO).
>
> The strange thing with your example is that I've always thought that VB 
> programmers - contrary to Access programmers - were quite familiar with 
> writing text files directly which, in this case, probably would be even 
> faster than writing DAO. Can't tell as I didn't study the code that 
> closely.
>
> Susan and editors have learned me to keep example code simple and free of 
> "smartness". Still, I think you always should try to educate the reader 
> that there is code and optimized code, and sometimes the optimized code is 
> only a small step away.
>