| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 29913 | 2003-02-05 22:51:00 | Access 2000 - combo box lookup delay | tbacon_nz (865) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 118689 | 2003-02-05 22:51:00 | Here's an interesting one - I have a data entry form for a survey where the possible response values are selected from a combo box. The possible values are always, mostly, sometimes, never. The values are derived from a response values table. The form is designed so that the focus moves to the next record as soon as the first character is entered (using on change). For most of the values, the data entry goes as fast as I can type, but if I type "s" for sometimes, the hourglass appears and there is a significant delay before the focus moves. If I cut "sometimes" in the lookup table down to "some" the problem goes away, and if I change "mostly" to "mostlyxxxx" the problem occurs on mostly. I don't understand why such a small change in the number of characters woild make such a large difference to the performance. As always, all insights will be gratefully received... |
tbacon_nz (865) | ||
| 118690 | 2003-02-05 23:25:00 | That certainly is very strange. Are you using a query, code or another method to derive the values to populate the drop down? | Dolby Digital (160) | ||
| 118691 | 2003-02-05 23:53:00 | The values are taken straight from a table of valid response values. I.e. the row source type is table/query and the row source is selected a "tblvalues", but I notice that access translates that into a select statement. The property for the table is two columns, col 1 is the numeric value, which is the bound column in the combo box, and col 2 is the text, 10 characters, which is the displayed text. Col1 is the primary key. Weird, eh? |
tbacon_nz (865) | ||
| 118692 | 2003-02-06 00:36:00 | This sounds gooky, but I have had the same problem with bound numeric fields - try (if you can) using a text field - for what ever reason it works faster. | wuppo (41) | ||
| 118693 | 2003-02-06 04:27:00 | tried that - makes no difference :( | tbacon_nz (865) | ||
| 118694 | 2003-02-06 22:42:00 | Hi, no definite answer Im afraid but a couple of things you could try... 1) Amend the Indexed property to yes for the field in the table 2) Compact the database - Ive had erroneous problems fixed by merely compacting & repairing. |
parry (27) | ||
| 118695 | 2003-02-06 22:49:00 | Done both of those... :( The issue is of academic interest, as the actual text is just a visual confirmation of the response - the number is what counts, and I can cut the text down to a size that doesn't affect performance. Still, I'd like to know what is going on... ?:| |
tbacon_nz (865) | ||
| 118696 | 2003-02-06 23:12:00 | For sure, like you I always want to know why. Whats your onchange event code got in it - perhaps post that and something obvious may be found. I would try another discussion board. Theres a site www.utteraccess.com which is Access specific so post there and a guru may know the answer. Theres also http: that has an Access discussion board but it only has a few posters in comparison - as the name suggests its an Excel site. Good luck :-) |
parry (27) | ||
| 118697 | 2003-02-07 03:17:00 | Thanks Parry, I'll try those groups. FWIW here is my on change code: Private Sub response_Change() Dim frm1 As Form Dim ctl1 As Control Set frm1 = Forms(Me.Parent.Name) Set ctl1 = frm1(Me.Name) ctl1.Form.Recordset.MoveNext End Sub Any thoughts? |
tbacon_nz (865) | ||
| 118698 | 2003-02-07 18:23:00 | Im by no means an expert on Axess VBA but it appears the combobox is a control on the subform. I couldnt get it to work perfectly but nevermind. One suggestion though - does your code work if you are on the last record when a change is done to the control? I could be wrong but Movenext may fail in this instance so you may want to test for EOF before this line. | parry (27) | ||
| 1 2 | |||||