I don't need this question answered per se - it's not affecting my program or anything - but I thought I'd ask it anyway to add to the growing knowledge base in the archives of this group. :-)
If you open a database, then do something inside the database, then go to open it again, apparently it causes no ill effects - I've done it. But if it's done repeatedly, are there any possible side effects to doing it, as in chunk overlocking, etc? Not necessarily chunk overlocking per se, but some sort of error that can come about? What my program had been doing was: Main Screen: open database, give 3 options(enter, edit, or view info) 3 options: enter, edit, or view info, then go back to the main screen (without closing the database) I recently realized, in a brilliant flash of 2am logic, that I hadn't been closing the database, but nothing had been happening - no error messages or whatnot. But, if I did it enough times, could something theoretically happen? Or does it just keep doing stuff to the same variable, the same location in memory, but not closing the database is just bad programming style? -C __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
