Re: Performance

No problem; the scope of temporary tables is limited to the process that created them. You can log in twice and perform the same select * from whatever into temp junk; and have no conflict over the name junk. The problem is that if you choose to have a permenant table called "junk" as well - that will cause it to spit its dummy. All the best, Pete Harris. } > } >To improve performance I broke the original query into 4 separate } >queries using the technique of substituting sorting in temporary tables } >to avoid nonsequential disk access. This technique is described in } >Chapter 4 of the INFORMIX "Guide to SQL Tutorial" - Using a Temporary } >Table to Speed Queries. (Lots of other good stuff in this chapter too.) } > } This is good. I've read about creating temporary tables and use them } for faster queries. But what about if two or more persons are using } the same data-entry screen? Will making a 'fixed' temporary table } name let one user succeed and the other one fail with a } 'table already exists' error? } } -- } - J - }