|
| Iniciado por guest, 26,mar. 2014 16:35 - 4 respuestas |
| |
| | | |
|
| |
| Publicado el 26,marzo 2014 - 16:35 |
Hi,
I have a combobox based on a query.
When I set the option to "direct access (no limit)" the list is truncated and the last entry is "##too many elements##".
When I set the option to "loaded in memory" no problem :confused:
This seems contrary to the "(no limit)" part of the direct access.
The solution is simple, but puzzling.
Regards,
Piet |
| |
| |
| | | |
|
| | |
| |
| Publicado el 26,marzo 2014 - 17:38 |
Hi Piet,
Extending your puzzle, why the setting "direct access" for a query anyway? A table on query enables sorting on all columns by default so the query structure must me already in memory so "loaded in memory" is some kind of redundant setting. In plus a table on query "loaded in memory" enable multiple sorting "CTRL + column header" while same query on "direct access" "downgrade" to one sorted column at a time.
My though is: "direct access" setting may insert unnecessary overhead in memory.
Adrian |
| |
| |
| | | |
|
| | |
| |
| Publicado el 26,marzo 2014 - 18:30 |
Hi Adrian,
I normally set all content to "in memory", this was one I accidentally overlooked and caused problems right away.
Regards,
Piet |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,marzo 2014 - 09:17 |
Hi Piet,
If you did not have any issues with "in memory" I will stick also with "in memory" as a best option.
Regards,
Adrian |
| |
| |
| | | |
|
| | |
| |
| Publicado el 05,marzo 2015 - 16:41 |
| Good day. Do not connect the combo file directly. Fill it by code. This way, you will not have problems. |
| |
| |
| | | |
|
| | | | |
| | |
|