Subform or listbox?

[Max Moor]

Hi All,
I want to list a bunch of records, then process those that the user
selects. I have to have multiple selections in this application (extended
type with control and shift selections), so I think that forces me to use a
listbox.

I like the idea, asthetically, of having the selectors at the side of
the records, highlighting which ones are selected, though. I need a
subform for those.

Is there a way to either make a listbox show selectors or to make a
subform do extended selections?

- Max

 

[ALESSANDRO Baraldi]

Hi All,
I want to list a bunch of records, then process those that the user
selects. I have to have multiple selections in this application (extended
type with control and shift selections), so I think that forces me to use a
listbox.

I like the idea, asthetically, of having the selectors at the side of
the records, highlighting which ones are selected, though. I need a
subform for those.

Is there a way to either make a listbox show selectors or to make a
subform do extended selections?

- Max

If you need of progressive selection without jump trough the records
you can use also SubForm and you the property SelTOP and SelWidth
and properly you have:

FirstRowSelected=Me.SelTop
LastRowSelected=Me.SelWidth
NumberOfSelectedRow=LastRowSel-FirstRowSel

I usually don't like this way, because with ListBox you always can
have JUMP selection, for each INDEX you know the content, and
the most important thing is that you can built in very easy way SQL
Criteria to put in QRY......!

Alessandro(IT)

 

[Van T. Dinh]

I would recommend a ListBox rather than a Subform. There are processes
running behind the Subform, e.g. AutoSave feature that can affect the Form's
operation. Also with Subform, I think you can only select a contiguous
block of Records, while with Multi-Select ListBox, you can select
non-adjacent Records.

Sorry, don't know how to put RecordSelector into a ListBox but selected
Records are highlighted (usually reverse-video) anyway.

 

[Mike Sherrill]

I want to list a bunch of records, then process those that the user
selects. I have to have multiple selections in this application (extended
type with control and shift selections), so I think that forces me to use a
listbox.

A listbox highlights each row you select. Listboxes don't have record
selectors.

When I can't see all the selections at one time, I prefer to use two
listboxes side by side. Clicking on a row on the left-hand listbox
inserts a row into the right-hand listbox; clicking a row on the
right-hand listbox removes that value. Then I process the ones in the
right-hand listbox.

 

[Max Moor]

A listbox highlights each row you select. Listboxes don't have record
selectors.

When I can't see all the selections at one time, I prefer to use two
listboxes side by side. Clicking on a row on the left-hand listbox
inserts a row into the right-hand listbox; clicking a row on the
right-hand listbox removes that value. Then I process the ones in the
right-hand listbox.

To All,
Thanks for all the answers. I ended up going with the listbox, as I
had to have the multi-select ability. I liked your idea (Mike) to use a
second box. I may do that somewhere else.

-Max

 

[Mike Sherrill]

I liked your idea (Mike) to use a
second box. I may do that somewhere else.

The VBA source code for Microsoft's Access 97 wizards used to be
available for download from www.microsoft.com. A lot of the A97
wizards used a pair of listboxes--might give you a jump on the coding.