Yes, more for people who are actually digging into the tables and creating stuff from them. That is not where I'm going. I want the end users to not have a clue as to how things work, or even what tables, rows, columns, views, and indexes even are! What I'm doing as I develop, I work on the most recent copy of my database, only while the main office database is shut down; that way I can rip away at stuff knowing that if something is wrong, I just recopy it and try again. I see the benefits in doing development through temp tables on the main database, but it scares me. I'm constantly backing up/reloading my database, several times a day and night.
On Thu, Jun 16, 2011 at 8:30 AM, Jim Belisle <[email protected]> wrote: > ** > > I my case, I use temp tables to do my processing, whether mathematical or > logical, before updating my permanent tables.**** > > It helps me follow my logic for complicated updates (such as inventory and > costing) by allowing me to see each step of my processing when I test the > code.**** > > Also if there happens to be a perceived (or real) problem once the code is > implemented, I can usually find the problem easier while tracing the code. > **** > > ** ** > > James Belisle**** > ------------------------------ > > *From:* **[email protected]** [mailto:**[email protected]**] *On Behalf Of > *William Stacy > *Sent:* Thursday, June 16, 2011 10:19 AM > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - temporary tables**** > > ** ** > > Is the push for using temp tables based on processing speed, data safety, a > combo, or what else? > > -- > William Stacy, O.D. > > Please visit my website by clicking on : > > http://www.folsomeye.net > > > **** > -- William Stacy, O.D. Please visit my website by clicking on : http://www.folsomeye.net
