On 2/15/07, johnf <[EMAIL PROTECTED]> wrote: > > So you would penalize all of us that do it right to accommodate the very few > who do it wrong?
No, I'm in favor of a flag, property or directive that lets the developer turn it on or off as needed. But I'd favor failing safe as the default configuration. And the 5% of us who do it right will have no trouble setting that flag. The 95% who might not even know about the flag won't have a problem with it. I don't agree that you are "penalized." This is SQL that's generated and sent to the back end. If you need to debug it and can't see your way through the quotes, I agree with the many other posters that there ought to be an option to turn it off. And I don't necessarily agree that some "do it wrong." If they really want a field named DESC, GROUP or FOR, well, then, they ought to have one without all this hassle. Similarly for fields with spaces, or other characters that might need to be escaped. Escaping all fields as a default is a design decision. > 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. Yes, I agree that it's rare. But it happens and it's annoying and confusing to the newbie. > 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. I really don't have a dog in this fight, and I won't fight this hard to dissuade you from your side of things. I generally avoid quoting myself, but note that some of the tools I use add it for me automatically. I don't see it as that big a deal. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
