NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: Rene Simons on June 03, 2019, 12:50:00 PM
-
Hi,
Is it possible when I enter a complete new value into an autocomplete field (value will not be shown as autocomplete),
to have that value added to the lookup file and have the form act as if the value already existed in the lookup file?
If so, how would I do that?
Cheers,
René
-
Adding a Lookup Button and setting in the Lookup settings tab the "Allow custom value not in lookup table"?
-
Hi Alberto,
That could be a solution but I insist on the autocomplete feature for ease of use.
It could be that you put me on a track that might be worth exploring however.
Thanks!
René
-
You can use Autocomplete with lookup button.
-
Hi Alberto,
I don't want a lookup button. :)
René
-
>> Is it possible when I enter a complete new value into an autocomplete field (value will not be shown as autocomplete),
to have that value added to the lookup file and have the form act as if the value already existed in the lookup file?
If so, how would I do that?
that feature is not currently in the system, so if you wanted to do that you'd have to code it.
I guess the starting point would be the Validate::whatever routine - the new value would come in there you can detect it's new and add the new row there if you like.
I suspect though this would lead to a LOT of "almost duplicate" records with bad spellings etc.
cheers
Bruce
-
Bruce,
>> I suspect though this would lead to a LOT of "almost duplicate" records with bad spellings etc.
I am fully aware of that but I am willing to take the risc. I don't expect that many records in that particular table.
Additional question:
At this moment, when I type a new value, (without your suggestion worked out), the entry field blanks out as soon as I tab to the next field.
Will this remain this way or will the new value be kept in the entry field, because the record now exists (after your suggestion is worked out?)
Cheers,
René
-
The "blank out" is coming from that same routine. You'll see it happen there (when the GetDescription fails.)
So your code should take care of that.
cheers
Bruce
-
Bruce,
I'll try and get back to you.
Thanks,
René