Hi Jim,
Why not defining a temp table instead a temp view You also can define indexes on this temp table. It looks to me that the state is used in the selection and if there is no index on it all records have to be inspected. If the number of rows are not changing during the session it might be worthwhile to consider to create and fill the temp table at another stage in your application Hope this helps a bit Tony From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: vrijdag 25 juni 2010 15:26 To: RBASE-L Mailing List 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
