NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: CaseyR on February 26, 2009, 01:42:42 PM

Title: Lookup problem
Post by: CaseyR on February 26, 2009, 01:42:42 PM

I am having a problem with one of my lookup buttons.

Here are the details:

I am using 4.31 and I have lost track of PR number but the SAF date was Feb 2 this year.

The table being looked up is a In-Memory table with a unique key, but the value needed by the calling form is not a component of the key.

The browse procedure, which is used solely to do this look up, displays the In-Memory records properly, but when Select is clicked the record is not selected.  Using the After Lookup, Before More Assignments embed on the calling form, reveals the record buffer of the lookup table is empty.  On the calling form, the look up settings are:

URL:      the look up browse procedure
From File:   the In-Memory table
Order by:   the unique key of the In-Memory table
Value field:  the field of the In-Memory table needed by the calling form


On the look up browse:

For the Table schematic:  the In-Memory Table with the unique key
Unique,unchanging key:     the unique key of the In-Memory table
Fields:   the value field and one other display field
On the Form tab, only the Select and Cancel button are checked.  A dummy form for the In-Memory table is entered as the Form control just in case

The dummy form has the In-Memory table with the unique key identified as the unique, unchanging key.

I should mention that the look up worked fine until the last NetTalk update, and that other lookups that have a physical table with the value field the same as the unique key component also work fine.

Unfortunately, this look up is required and central to the application function, so any help would be greatly appreciated.  Thanks in advance.

Title: Re: Lookup problem
Post by: kevin plummer on February 26, 2009, 05:01:23 PM

Your best bet it to just download the latest version and recompile. Although I haven't updated myself, I don't recall too many complaints about bugs/regressions with that version on this website. If it is still a problem then send a small example app to Bruce.

Title: Re: Lookup problem
Post by: CaseyR on February 26, 2009, 06:14:30 PM

Thanks for the suggestion, Kevin.

Title: Re: Lookup problem
Post by: CaseyR on February 27, 2009, 12:58:25 PM

Unfortunately, updating to PR 32 didn't solve the problem. So if anyone has any other suggestions, I would really appreciate them.

Thanks.

Title: Re: Lookup problem
Post by: Bruce on February 28, 2009, 01:05:12 AM

I'll be uploading PR33 today. This specifically fixes a problem in lookups where the field being looked up is not the primary key field of the remote table.  It may also fix an issue in lookups in other cases as well.

Cheers
Bruce

Title: Re: Lookup problem
Post by: CaseyR on February 28, 2009, 07:59:13 PM

Thanks, Bruce