Update: Windows Secrets newsletter references this issue and links to a couple of discussions. http://windowssecrets.com/2010/12/16/07-PC-patches-end-this-year-with-a-bang

TRANSFORM(eExpression, [cFormatCodes])
TRANSFORM( "2175551212", "@R (999) 999-9999") && Result is "(217) 555-1212"
CREATE TABLE myTable ( cPhoneNbr C(20))A format mask of "@R (999) 999-9999" works for the first value but returns garbled results for the other two. For the U.S. phone number without an area code, a format mask showing a blank area code would be more appropriate, while for the international number it may be best to use no format mask at all and just display the number the way it was entered.
INSERT INTO myTable ( cPhoneNbr) VALUES ( "2175551212") && U.S. phone nbr w/ area code
INSERT INTO myTable ( cPhoneNbr) VALUES ( "5551212") && U.S. phone nbr w/out area code
INSERT INTO myTable ( cPhoneNbr) VALUES ( "+46 704123456") && International phone nbr
lcPhoneNbr = ALLTRIM( myTable.cPhoneNbr)
DO CASE
CASE LEN( lcPhoneNbr) = 10
lcResult = TRANSFORM( lcPhoneNbr, "@R (999) 999-9999")
CASE LEN( lcPhoneNbr) = 7
lcResult = TRANSFORM( lcPhoneNbr, "@R ( ) 999-9999")
OTHERWISE
lcResult = lcPhoneNbr
ENDCASE
TRANSFORM( cPhoneNbr, ;
ICASE( LEN( ALLTRIM( cPhoneNbr)) = 10, "@R (999) 999-9999", ;
LEN( ALLTRIM( cPhoneNbr)) = 7, "@R ( ) 999-9999", ;
""))
TRANSFORM( myTable.cPhoneNbr, GetPhoneNbrMask( myTable.cPhoneNbr))
Today I finally found time to carefully read the evals from my sessions at Southwest Fox. Thanks to all of you who attended one of my sessions and took the time to comment. To those who had good things to say, thanks for the kind words. To those who suggested ways in which I can improve, I genuinely appreciate your suggestions.
A Speakers' Dilemma
One thing I always wrestle with is how much content to try to fit into the allotted time. Like most speakers, I try to provide maximum content and hence maximum value in all my presentations. Sometimes, however, that comes at the expense of not leaving enough time for questions. Several people commented that this was a problem with both my sessions at Southwest Fox this year, and I want to let you know that I hear you.
I generally ask that questions be held until the end of the session. The reason for this is to ensure there's enough time to cover all the material. You might be surprised at how easily taking the time to answer just a handful of questions during a session can derail a carefully timed presentation. However, I realize that if I ask for questions to be deferred until the end, I'm also making an implicit agreement with the audience to leave enough time for those questions.
So, here's my main take-away from this year's evals: I need to be sure to leave time for Q & A even if it means trimming the session content a bit. As I think about it, that's a better formula for maximizing the value of a session anyway, because all of us (speakers included) learn from each other's questions. Besides, the white paper provides a place to put relevant content that doesn't fit in the verbal presentation.
A Question
I think leaving around five minutes for Q & A at the end of a 75-minute session feels about right. Any less is almost certainly not enough, while significantly more means that much less session content. But that's just my opinion. What do you think?
An Apology
To the person who came up to me at the end of my Friday afternoon session on the FoxPro Foundation Classes: I apologize for putting you off and rushing out of the room. I had come down with some kind of 24-hour bug Thursday evening (and no, not from too much partying - really!). I was feeling pretty rocky all day Friday, and to be honest I wasn't sure I was going to make it through the entire Friday afternoon session. I came pretty close to losing it immediately after I finished speaking, and had to rush out of the room for a couple of minutes. When I got back, you had already left. If you are that person, I hope you will understand, and if you still have a question please e-mail me and I'll be happy to try to answer it.
Tags: Southwest Fox, SWFox, conferences, presentations
This is a real error dialog from a real app. Not a beta release, either. And no, I didn't capture the screenshot before the dialog was fully rendered - this is the whole thing. (I did add the caption, though.)
So we're not only left to wonder what the error was, but also what application had the error in the first place. Huh.