On Wed, Jun 29, 2011 at 7:05 PM, smplx wrote: > > Thanks! Open/close on an as-needed basis it will be, then. But at any > rate, > > it's a small project with only a few users (not more than two or three = at > > the same time) so I won't be exhausting any modern SQL server no matter > how > > bad I code it. > > FAMOUS LAST WORDS! > > :-) > Hahaha that's pretty funny. ....but no. Modern servers can handle MANY connections. I'll have to *try* to make it crash. > FAMOUS LAST WORDS! I hate when people say that. You can expect with a reasonable level of certainty that whatever you're working with won't crash as long as you're operating within its specifications. That's they key. And I am operating within specifications. I was only asking about good/bad/general coding styles for database program= s and how it's *generally* done. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .