Dan,
I did index most of the columns sales desires to use. Two of the columns are NAME columns, ship to and sold to. Since they are long text names, should I still index them? I just changed the WHERE to use LIKE instead of CONTAINS. It is hard to tell from here (off site) but it seems faster. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Dan Goldberg Sent: Friday, February 12, 2010 10:01 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: ON KEY PRESS This is refreshing you list based on the where clause. It sounds like your where clause in your variable list view needs to be looked at. I have a form that uses on key press and a variable list view. It shows parts we currently use. What I did to speed it up is to have it create a temp table with only the columns displayed in the variable list view and filled it with only current parts. I takes a second or two to create temp table before the form opens but it moves really fast!! Dan Goldberg PS You also might look at the columns in your where clause in your variable list view. Make sure those are indexed. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Friday, February 12, 2010 7:42 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: ON KEY PRESS Back a month ago, many made suggestions regarding the speed issue I had with my On Key Press. I added a Variable Radio Group, set a Primary key and Indexed some columns the sales people would use most frequently. Nothing helped with the speed. I just now got back to testing the code and found the hangup occurs on this line, PROPERTY LV_Quotes REFRESHLIST 'TRUE' This component ID LV_Quotes relates to a variable list view. The list view has eight columns it brings up from one table, OrderHeader. Everything else goes quickly but when it gets to this line, things bog down. I do not know what else to do since I assume I do need to refresh the list after each keystroke. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Michael J. Sinclair Sent: Monday, January 11, 2010 12:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: ON KEY PRESS Put an index on the field(s) that are being selected by the OnKeyPress...it works like lightening. Also, if you have the code that was offered originally the Rbase User that created it, I found some parts of the code did not work or generated errors which slowed it up a bit. I found them by tracing the application. You should do the same so you can see which line or lines are causing the delay. Mike -------------- Original message from "Jim Belisle" <[email protected]>: -------------- Jan & Larry, I do not have indexing on any of the fields. Being a novice at programming, I watch the list when questions come through on indexing and am confused as to when to use them. It seems in some instances the list says not to use them and in other use them. I will have to try that. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Monday, January 11, 2010 11:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: ON KEY PRESS << I am using the On key press feature to edit orders. The orders table has 20,000 plus rows and it is taking ten seconds or more for each keystroke to search the records. What can I do to make the process faster? I just updated to the latest 7.6. >> What is the search you are executing in the ON KEYPRESS event? If it's non-indexed, expect it to take a few seconds. -- Larry
