Re: It's incredible

In article <3n3umc$9ch@cssun.mathcs.emory.edu> corinne@asix.com (Corinne Gregory) writes: > >My only comment to this is...name me ONE PRODUCT (DATABASE OR OTHERWISE) >THAT DOESN'T HAVE BUGS!!! I defy ANYONE to write any application (using >ANY PRODUCT) that won't have a bug in it. If YOU can't write bug-free >code, why in heaven's name would you EVER expect anyone else to do it??? > >Now, can we Puh-lease get back to our regularly scheduled programming? This >is, after all, a forum for questions and answers. If you want to sling >mud, go behind the barn. Most of us have real work to do. > Funny, I've got 500K+ lines of 4GL code *stuffed* with outer joins. Never seen a problem. Informix has more bugs than I like. *MY* code has more bugs than I like. (I like 0 bugs :) ). The implied assertion is the opposition products don't have bugs, which is obviously a joke. I, for one, have used Oracle, Sybase, Progress and Informix. I have the least problems with Informix. On to NewEra, it's a 1.0 release. Of course it will have unresolved bugs and logic traps that made it through beta testing. BUT, IMO the re-engineer the language is the *right* approach. I have just written/generated 6.6Mb of source in a competitor's GUI language fitted onto their procedural language. It works but it isn't elegant. NewEra strikes me as a language that had a good design philosophy in place first. And a tip, learned the hard way (not in NewEra): watch your transaction scope very carefully in event driven programming. Running modeless windows means the user can go and perform a totally different set of work in the middle of data entry and this will be included in any open transaction. If it gets rolled out, it *all* gets rolled out. Needless to say, this is very embarrasing if the transaction scope starts at the main menu :). Don't know what the long term solution to this is. I suspect we need named transactions, so you can have more than 1 open. Meanwhile, I scope all my data mods to happen on press of a OK or DONE button so I can ensure the user isn't wandering off in the middle.... Peter Wiley