Thanks, Mike, I'll work through your solution tomorrow - I wouldn't have thought to start with zero, either, at least, not straight away so that's saved me some head-scratching!!
Just to pick up on your response to my third point, I don't think it matters too much whether there were a DB or a Variable multi-selection object but, obviously, both would be nicer. Nor, I think, would it matter if it returned a comma separated string. After all, SSUB & ITEMCNT are built specifically for that option. Of course, a combobox is not so easy but it takes up less space on a form. I'd be happy with any "simple to define" object along the lines of the currently available choices. I've said it before and I'll happily say it again: the DBLookUpComboBox is one of the best new features of v7 and saves so much time in form design - especially now that the speed of forms is comparable to previous versions. I said it privately during beta-testing but it's worth saying publicly now that upgrade #78 has been released: thank you to RBTI for this improvement to the speed of forms - it really is a huge advance. Regards, Alastair. ----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, November 29, 2004 7:29 PM Subject: [RBG7-L] - Re: CHKBOX funtionality in Forms > Answers In Line... > > ----- Original Message ----- > From: "Alastair Burr" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, November 29, 2004 2:09 PM > Subject: [RBG7-L] - Re: CHKBOX funtionality in Forms > > > > Hi Mike, thanks for this but please could you confirm a couple of things for > > me? > > > > Firstly, it seems that clicking on the "Check Selected State..." button > > gives the selected numbers in the pause ok but does not put them into a > > variable. Is that intended or am I missing something. Typing those numbers > > into the vListSet field and then clicking on the "Toggle" button does > > produce a variable with the numbers. > > Once you know the Index number of an item, you can retrieve the "Displayed" > value of the item Like: > > 1. if the index number of the item in a "selected state" is in a variable > "vIndex" > > 2. Then you locate the item in the list to act upon via > Property <compID> itemindex .vIndex > > 3. To get the value of that item into a variable "vItem" > GetProperty <compID> Selection 'vItem' > > > > Secondly, am I right in thinking that the number returned (whatever way) is > > the sequence number in the list? If so, is there no way at all that it could > > return either the text (comma separated) or something a little more friendly > > to work with? > > The number returned is the index number of the Item in the List, beginning with > the "First" item at Index "0". Most Controls that have lists are Zero based, > so the "Sixth" item displayed in the List is at Index "5" (DisplayLocation - 1 > = Index#) > > > > I've got it working with my table and data quite happily but it's going to > > be interesting <g> to work out how to select the corresponding id for each > > selected item of text from the position in the list. > > Use the method above... > > > Thirdly, and I realise you might not know but maybe Razzak can confirm or > > otherwise, is RBTI working on some sort of "MultiSelectUserDefinedListBox" > > or "MultiSelectDBLookUpComboBox"? If not, it sounds like one needs to be > > added to the wish list on the website. > > Bound controls wouldn't accept Multiple selections very well, unless you wanted > to save a comma separated string to a column, so I don't think this > functionality will migrate to any control that is not a variable type control. > Also, when multi select is made, it is up to the programmer to assemble the > selected items into a string. > > And Comboboxes by their very nature, don't lend themselves to a very friendly > multiSelect. You can manipulate the size of a ListBox and a command button to > mimic a Combobox DropDown and Rollup somewhat if you just had to have it, but > again, ComboBoxes don't do MultiSelect very well..... > > > Again, thanks for this, I'm sure I can make use of it, > > Regards, > > Alastair. > > > > > > > ----- Original Message ----- > > From: "Alastair Burr" <[EMAIL PROTECTED]> > > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > > Sent: Thursday, November 25, 2004 8:48 PM > > Subject: [RBG7-L] - Re: CHKBOX funtionality in Forms > > > > > > > Many thanks - I'll take a look at it over the weekend. > > > > > > Regards, > > > Alastair. > > > > > > > > > ----- Original Message ----- > > > From: "MikeB" <[EMAIL PROTECTED]> > > > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > > > Sent: Thursday, November 25, 2004 8:12 PM > > > Subject: [RBG7-L] - Re: CHKBOX funtionality in Forms > > > > > > > > > > > > > > > > > > > Thanks, Mike, but please could you do me a favour and either re-post > > or > > > send > > > > > me privately that example? > > > > > > > > > > Also, I have been experimenting today with a "Variable LookUp Listbox" > > > but > > > > > you talk of a "User Defined Listbox" - will your solution work on > > both? > > > > > > > > http://www.byerley.net/multiSelectForm.zip This is the Example I was > > > referring. > > > > > > > > This Only works on a Variable User Defined ListBox, but there is nothing > > > that > > > > *Can't* be done using it, except employ the MultiSelect when you use > > > > Expressions for Lookups. > > > > > > > > In other words, just use a Declare Cursor and the ListItemsADD Property > > to > > > > populate the ListBox or do a Select to a file on disk, and use the > > > > Load_From_File property to populate it. > > > > > > > > Then MultiSelect works perfectly. > > > > > > > > > > > > > > > > > > Regards, > > > > > Alastair. > > > > > > > > > >
