In my app end users know how to handle the phone, patients, appointments, payments and the like. I can't imagine them ever doing any table level stuff. Plus there's the issue of data loss. Transactions in medical apps need to be remembered with paper (virtual paper, that is) trails, etc. Deletions and revisions after the date of transactions are not permitted.
On Thu, Jun 16, 2011 at 10:38 AM, Dan Goldberg <[email protected]> wrote: > ** > Temporary tables are only seen by the user that created them. So each user > can have unique data that pertains to them looking at the same form. > > Speed is definitely a plus at times. > > Sometimes I use temp tables to organize and format the data before the > report generates the output. > > It just depends on the need. I use them all the time. > > Dan Goldberg > > *From:* William Stacy <[email protected]> > *Sent:* Thursday, June 16, 2011 8:18 AM > *To:* RBASE-L Mailing List <[email protected]> > *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
