Drop fields - Two questions

[GFasolt]

I have several NetWebForm procedures with drop fields that look up values form other files. In all cases the child table is related to the parent by an ID (i.e., MEM:MemberID LONG), with relations defined in the dictionary), not the displayed value (i.e., MEM:Name STRING(30)). Two questions:

1) NetTalk does not appear to update the parent record with the ID from the child after making a selection from the drop list. How do I handle this?

2) When opening the NetWebForm, the look up fields contain the wrong values unless I load the correct record soon after the CODE statement. Is this normal or am I doing something wrong?

[Bruce]

Hi Greg,

There are several examples that do this - like (from memory) the shippers & countries from example 31.

So sounds like yours is slightly different to the norm. Could you make a small example?

cheers
Bruce

[GFasolt]

Hi Bruce,

Thanks for your reply. I spent quite a bit of time with example 31, but not lights came on for me (BTW, the example was saved in local mode and so initially caused a small explosion of compiler errors).

As requested, I have created a demo app, which I'll send to the support address at Capesoft since it includes some real data.

As to what I'm doing being unusual, I don't think so; rather, I've probably not explained myself well.

1) First tab in my form example has a simple drop used to select the MemberType, where the relationship is Members <>> MemberType. This is still troublesome.

2 The second tab includes a browse displaying an alias for Members that is linked to the current Member by a many-to many linking table. The update for this uses a drop with a link table with which I am haveing trouble.

In both cases, the value displayed is a STRING field, but the linking fields are LONGs