Page 1 of 1

Lookup fields problems in 5.30

Posted: 2014-06-05 10:06
by gerardus
Hi,

I installed version 5.30, re-opened a project that I had started with a previous version of AppGini.
I create a lookup field that references a record in a new table, and when I click on the listbox to select a record, all I get is an empty lisbox with "Searching..."
The key field types are identical (integer) and the reference is set correctly (I think) in the lookup field definition.
Any idea of what I'm doing wrong?

best regards,

Gerard.

Re: Lookup fields problems in 5.30

Posted: 2014-06-05 10:13
by gerardus
By the way,

when editing the lookup field properties, Advanced | Advanced Lookup options | Reset to default query fails with the following error:
"Runtime error '5': invalid procedure call or argument" and then the program exits.

Re: Lookup fields problems in 5.30

Posted: 2014-06-05 15:59
by pvisser
Same Here. I have the same problem..

Re: Lookup fields problems in 5.30

Posted: 2014-06-07 15:14
by a.gneady
For the first problem (empty drop down), please make sure the iconv extension is enabled in your php.ini configuration file.
For the other one, I need to inspect the project file causing this issue. Please send it to support at appgini dot desk-mail dot com

Re: Lookup fields problems in 5.30

Posted: 2014-06-09 09:27
by mjcargill
Hi,

I'm experiencing the same problem - and iconv is installed.

Re: Lookup fields problems in 5.30

Posted: 2014-06-09 21:57
by AhmedBR
I had a similiar problem, maybe yours is the same:

Check if you are using a custom query in the Advanced lookup options.
If you are, then Reset to defalt query and redo your custom query.
In my case this did the trick.

Re: Lookup fields problems in 5.30

Posted: 2014-06-10 07:49
by gerardus
Hi,

here's the relevant output of php -i:

iconv support => enabled
iconv implementation => "libiconv"
iconv library version => 1.14
Directive => Local Value => Master Value
iconv.input_encoding => ISO-8859-1 => ISO-8859-1
iconv.internal_encoding => ISO-8859-1 => ISO-8859-1
iconv.output_encoding => ISO-8859-1 => ISO-8859-1

So, it seems that iconv is enabled.

I deleted the MySQL DB, re-created it with the default charset utf8_spanish2, started a new project with two tables and now it works.
I am going to ditch the old project file and stat with a fresh one.

Best regards,

Gerard.