On Thursday 15 February 2007 11:14, Ted Roche wrote: > On 2/15/07, johnf <[EMAIL PROTECTED]> wrote: > > Instead of lowering ourself to the lowest denominator let us ask the user > > to raise his/her level to a NORMAL standard. If they have to be abnormal > > then they can turn on quoting. > > John: > > This isn't the way to try to get dabo accepted into an enterprise. If > I'm coming in and want to help the client raise his standards, it > helps a lot if I can set the client up with dabo and the AppWizard and > It Just Works. Later, we can explain to them that "GROUP" and "DESC" > and "SELECT" are bad field names, along with teaching them about > normalization, program design and so forth. > > If a newbie logs on and tries to run the app and it crashes (with, to > the user, obscure error messages), the newbie's conclusion is: (1) > it's too hard, (2) dabo is buggy or (3) it won't work for me. > > Many of my clients are self-taught SMBs and the fact that they've made > millions of dollars and kept people employed has to be balanced > against their ignorance of some best practices. If we start by > slapping their wrist, it's the last we'll see of them.
So you would penalize all of us that do it right to accommodate the very few who do it wrong? I'll grant that my exposure to database schema is limited. But I can only recall a few instances where quoted field names in a SQL statement was required. Your experience may be different. Less assume that your self-taught SMB is using Dabo. They would use the ClassDesigner to create their forms or AppWizard. Within both ClassDesinger and AppWizard we can ask the user if they want to use quoted SQL statements. But that is different than defaulting to TRUE. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
