This seems to be the week that things I thought I understood stop working...or my understanding is not what I thought. Very glad it's Friday...
View's first column is sorted/categorized
I can currently use @Unique(@DbColumn(...)) to display to the user all values in the first colume for selection and subsequent use.
Eventually, this is going to fail when we cross the 64K barrier so I'm looking for an alternative (*).
I want to give the user a pop-up that contains only a subset of values based on some key they type in.
Assume I have data as follows in col 1:
User enters '001-' as the key and I want both '001-' entries to be displayed for selection.
What we get is only the first entry.
I've looked at designer help and there is nothing that says 'partialmatch' drops you to one returned value.
I've searched the forum and also found nothing that says 'partialmatch' limits the returned data.
So does PartialMatch force you down to one hit on the dblookup or is something else going on? Code below.
TIA for any help.
Key := @Prompt([OkCancelEdit];"Lookup key";"Enter the first few characters of the folder you want to open";"");
PNList := @Unique(@DbLookup("Notes":"NoCache";"";"vwPNPicker";Key;1;[PartialMatch]));
PN := @Prompt([OkCancelList];"Pick PN";"Select the folder you'd like to open";"";PNList);
(*) For anyone who's curious, this is the same db where my @Picklist has gone crazy.
I'm trying to find another way to future proof the db and fix whatever is going on with @Picklist.
The db's first column currently contains over 10,000 entries with the shortest being 6 characters and most being around 12 and some upwards of 30.
Sometimes page 2 of Google is your friend.
Found this link
Which led to this link:
Sort the view, drop the category and it works
Jake, thanks for the post, thanks for leaving it up, and IBM thanks for keeping the link alive all these years!