NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: CaseyR on June 07, 2012, 08:35:15 AM

Title: Problem with optional lookup
Post by: CaseyR on June 07, 2012, 08:35:15 AM

I am pretty sure a bug has been introduced in the optional lookup function for string fields.   When a string field has a lookup, if you enter the value manually the value is cleared when you move to the next field.  If you use the lookup for the entry it  works fine. The 'Force users to use lookup' is turned off.

I use the optional lookup in a few places just to save users key strokes rather than enforce edit controls.  I have been able to reproduce the problem on a couple of form templates. It is also visible in the Update Appointment procedure in the Hot Dates example, although in that case such a bug would actually provide some edit control benefit. 

Release 6.18 did not have this problem.  Currently using release 6.31 but I don't recognize the problem in the release notes of 6.32 or 6.33

If it is not a bug, how do I restore the optional functionality?

Many thanks. 

Title: Re: Problem with optional lookup
Post by: Bruce on June 07, 2012, 09:00:16 AM

Hi Casey,

just to be clear - by "optional lookup" you mean where they _might_ select something from the lookup, but then again they're free to just type in whatever they like?

ie a sort of "unvalidated" lookup?

cheers
Bruce

Title: Re: Problem with optional lookup
Post by: CaseyR on June 07, 2012, 08:58:42 PM

Yes.  The user has the option of keying in the characters or using the look up to select an entry.  No validation, just free form text.  That has been the NT functionality for a few years.  It just stopped when I updated to 6.31

The SV Win32 templates let you specify that a keyed in entry is checked against a lookup table and rejected if the keyed in value wasn't in the table.  Useful, I guess, but not what I need.  If that is now the default functionality of NT is there any way to work around it?

Thanks.

Title: Re: Problem with optional lookup
Post by: CaseyR on June 22, 2012, 01:31:09 PM

Hi, Bruce

A little more on this problem.  Turns out it is not a data validation issue at all.  The results I saw were just a fluke from working with a small test data set.

Rather, the problem is that loc:lookupdone is set to 1 when the user moves to another field by pressing Tab or clicking on another field after keying in a value.  Then the AfterLookup routine puts the lookup field value (usually blank) into the form display field clearing the value that was just entered.

Thanks