Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 61 to 63 of 63 total |
What's Coming Up with ElevateDB 2.0 |
Thu, Jun 19 2008 9:16 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | John
>Unless you use .clear extensively in your application surely all thats need >to be done is to make all char/varchar fields not nullable with a default >expression of ''. I do make extensive use of .Clear and .IsNull and a simple search and replace is not possible since this also applies to non-string fields. Also if I finally decide on the emptystring default I have to review and possibly change all of my handwritten SQL and that which is programmatically generated plus alter and my query generator. If you search the ngs you'll find I have posted a fairly detailed list of what needs doing. My problem is that I made extensive use of DBISAM specific features and the switch to ElevateDB is nowhere near as straightforward and simple as I originally thought. If it were easy and simple I would not have complained at all let alone as vigorously as I have. >How about showing of you edb SQL skills with a generic procedure for all the >null<>emptystring haters <vbg> Did that before I thought null=emptystring was going to make it into V2. If I can find it I'll post it in the extensions ng. Roy Lambert |
Thu, Jun 19 2008 12:47 PM | Permanent Link |
"David Cornelius" | > Say someone typed an answer, realised they'd answered the wrong question
> and deleted it, answered the right question and then decided they didn't > want to answer the other question after all....... > There was almost always an option called "Not given" or "unknown". We didn't really care about WHAT the answer was (no wrong answers), but simply wanted to know if the question had been addressed. If the subject did not want to answer it, there was a way out. Other than that, there was no way to "unanswer" a question--but that was by design (we actually did discuss it in design meetings and could have provided a button to reset a question to NULL). -- David Cornelius CorneliusConcepts.com |
Thu, Jun 19 2008 1:57 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | David
Hmm he says suspiciously - that sounds pretty much how the government conduct surveys over here. The only real difference is not only can you not unanswer a question they're already either answered for you or they keep asking until they get the desired answer. Pretty much like the EU want to do in Ireland - your referendum gave the wrong answer - please try again. Roy Lambert |
« Previous Page | Page 7 of 7 | |
Jump to Page: 1 2 3 4 5 6 7 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |