I will definitely experiment with that. I use temp tables in come of my command files that do a lot of calculations.
That may be the way to go. jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Friday, June 25, 2010 10:04 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: cursor speed Jim, Without knowing all the details I would encourage to explore other options. Cursors are slow. Consider the use of temp tables to build your view. Sometimes I will have several temp tables that I build a temp view on. They are faster because they are no local. I don't mean to disparage cursurs. Sometimes they are the only way to get what you need. Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Fri, 25 Jun 2010 08:26:11 -0500 Subject: [RBASE-L] - cursor speed Within a form I create a temp view that is created very fast. This view is a total of 2700 rows long at this time and will grow as the year progresses. This view has only four columns. I then use a cursor to create hints based on the 50 states and DC. When testing this in a single user environment, it is lightning fast. The minute someone else logs on, it takes upwards to 3 minutes to create the hints. Two of the fields are FK indexes. But the State field is not. Can you index a field in a view "on the fly" so to speak and will that give me more speed? Or would it be best just to go ahead and put a permanent index on the table? If this may not be the problem, I will listen to any suggestions. Jim
