Years ago when I was in college, I worked as a Lab Assistant in the computer lab (TRS-80, CoCo's and Kaypro computers, BTW!) . Every student on campus was required to take an intro to computer programming course and our job as Lab Assistants was to assist students of all different backgrounds and fields of study work out their programming issues from this class.
One of the first rules was "Don't solve their problem TOO fast!" If a Lab Assistant walked over to a student who had been in the lab for 6 hours struggling to overcome a syntax error and we walked over and immediately pointed out the comma in the wrong place, the struggling student might get angry enough to just get up and walk out. However, if we took a little bit of time to locate the problem and asked them lots of questions about what they were trying to accomplish and THEN we pointed out the errant comma, they accepted our correction more easily and their pride was still intact and they didn't get too frustrated with the whole concept of programming. Somehow yesterday I forgot to look for an "errant comma". PS: Thank you Ted for not solving my problem TOO fast! I might just stay with Foxpro for another 25 years. :) Paul H. Tarver -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche Sent: Thursday, November 16, 2017 9:05 AM To: [email protected] Subject: Re: SQLite Problem - DSN-less Connection Doesn't Create A File On Thu, Nov 16, 2017 at 9:39 AM, Paul H. Tarver <[email protected]> wrote: > Ok, I formally nominate Ted Roche to be VFP King and SQLite Guru! All > those in favor? :) Aw, shucks. "If nominated, I shall not run. If elected, I shall not serve." -- LBJ "It's good to be king." -- Mel Brooks, The 2000 Year Old Man. I'm just the editor of the SQLite book doing a little CYA to make sure I hadn't lead anyone astray. > Around > here they say, "If it had been a snake, it would have bit me." It's been my experience fixing my own and other's stuff that we're really good at getting the complicated stuff right, and really bad at finding the misplaced semi-colon or mistyped command. > One weird thing remains: "Have you tried turning it off and back on again" -- The IT Group It's almost impossible to guess. Perhaps you had an ON ERROR * in code you ran two days ago. It's always helpful to turn the machine off and on, and to try to reproduce with as few lines of code as possible, and on a different machine if possible. > Thank you Ed for providing the ProFox list. Without this place I don't > know how long it would have taken me to figure this issue out if ever. Hear, hear! -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
