Multi-part key in a control (OpenInsight 32-Bit)
At 10 APR 2002 06:35:19AM Ray Chan wrote:
In AREV, I could enter a two part key into a prompt, e.g., 02085*3067.
However, when I do this in OI, it seems that all I see at the LOSTFOCUS is only the first part of the two part key, e.g., 02085.
Is this normal for OI? Is there a way around this?
Thanks,
Ray Chan
At 10 APR 2002 07:03AM B Strom wrote:
Hi Ray,
In the form, check detail for key part, set the first key as 1 and secound as 2 etc. we use 2 and 3 multi-part key and it works fine.
Regards
Bertil Ström
At 10 APR 2002 11:22AM Don Miller - C3 Inc. wrote:
Ray ..
Is the bound control for the field the WHOLE key or just a part of it? E.g., bound to KEYP1 or something like that?? If so, then it will find the data to the left of the '*' and use it. Usually, I get multi-part keys with different prompts. If you define a dictionary item as WHOLE_KEY or something like that and make it Field #1, with no parts, you should be OK. Sometimes Table Builder will alias a key field to one of the parts which will defeat a "whole key" definition. Just a thought.
Don
At 10 APR 2002 05:01PM Ray Chan wrote:
Don,
Is the bound control for the field the WHOLE key or just a part of it? E.g., bound to KEYP1 or something like that??
The bound control is for the whole key. We have one form in AREV like this. All other forms with mult-part key have multiple controls. However, to maintain backward compatibility with our AREV app, we kept it the same in OI – one control for the WHOLE key.
If you define a dictionary item as WHOLE_KEY or something like that and make it Field #1, with no parts, you should be OK.
WHOLE_Key – where is this?
If I understand you correctly, you're suggesting that I make the key field FIELD #1. I can't do this as we already have a FIELD #1. Are you saying that you can put a key field into something other than 0 (zero).
Thanks,
Ray
At 10 APR 2002 10:58PM Don Miller - C3 Inc. wrote:
Ray ..
The problem I alluded to is that sometimes if you've defined a dictionary initially as KEYP1 .. field 0, part 1; KEYP2 .. field 0 part 2; KEYP3 .. field 0 part 3 before you define the @ID or someother field that will be the key, then I've seen table builder alias the new field to the first part of field 0 (KEYP2) with the SYN property. Then if I use this element, I only get the first part of the key. I have had to go into AREV to fix it. Just a thought.
Don
At 21 APR 2002 07:46PM Ray Chan wrote:
Don,
I have had to go into AREV to fix it. Just a thought.
Just a thought, but how do you go into AREV to fix it. The table itself was brought over from AREV 2.0x. What is it about AREV that would allow you to "fix" this that you can't do, for example, in OI's system editor.
Thanks,
Ray