Home/ Questions/Q 8855683
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T14:11:29+00:00

I’m trying to implement multiple record selection feature on a grid. It is very

  • 0

I’m trying to implement multiple record selection feature on a grid.
It is very similar to http://www.tek-tips.com/faqs.cfm?fid=3831
It adds an extra column with check boxes. I want those check boxes!!

But it depends on a extra logical field in the underlying table. It need to create a class clscheck which inherits CHECKBOX. I’m not sure why this CLICK procedure is needed for the checkbox. 

 PROCEDURE CLICK
    IF DODEFAULT()
        KEYBOARD '{DNARROW}'
    ENDIF
 ENDPROC

When I removed it, row selection did not work correctly as expected. Why this?

Here is my requirement:
1) I don’t want to add an extra logical field in the underlying table.
2) To work with controls in the grid, I think AllowCellSelection must be .T. I want AllowCellSelection = .F. because I don’t need to work with any control in the grid except the check boxes. I need to work only with check boxes. The other columns will be read-only.
3) Can I have selected list without the logical field in the underlying table?
4) Can I remove the usage of KEYBOARD ‘{DNARROW}’?

In fact, I have a grid which is AllowCellSelection = .F., but it only provides single selection.
I need to enhance it with multiple selection, thus, I just want to add an extra column with check boxes so that user can know he can select multiple records.
No need Shift+Click or Ctrl+Click which is not familiar with idiot users.

I have found this – http://www.tek-tips.com/faqs.cfm?fid=433
It also depends on an extra logical field and it depends Shift+Click and Ctrl+Click.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you are seeing is quite common for multi-select grids. I’ve used them SIMILAR to this in the past. However, you are afraid of the extra column in the underlying table. That may/not be true. You don’t always have to update the ORIGINAL table, but a temporary CURSOR you are presenting to the user. Ex: If you want to display a list of employees in a table. No, you don’t want to keep adding this column to the original employee table as then anyone else trying to do multi-select could falsely get your selection. However, if you pulled into your own local cursor and presented to the user, then no problem. Example…

    Thisform.YourGrid.RecordSource = "Employees"
(bound directly to your employee table -- not necessarily the right thing)

    vs

    use in select( "C_MultiPickEmployees" )
select ;
      .F. as IsChosen, ;
      E.* ;
   from ;
      Employees E;
   into ;
      cursor C_MultiPickEmployees READWRITE

Thisform.YourGrid.RecordSource = "C_MultiPickEmployees"

    NOW, you have your extra column without dealing with issues to the underlying table. If you wanted to further filter what you were showing — such as employees for a certain division/department, then just add that to a WHERE clause, add an Order By if so needed and you are good to go.

    As for the “Allow Cell Selection”, I’ve never had to deal with that. I just add a “checkbox” to the first column and set

    Thisform.YourGrid.Column[1].CurrentControl = “CheckBoxControl”
    (based on the name it is added to the column).

    Then, set the column 1’s “ControlSource” = “C_MultiPickEmployees.IsChosen” and you should mostly be done.

    As for the “CLICK” event trying to force the down arrow. This is more for automatically scrolling to the next record so you can just click, click, click for multiple entries.

    Hope this helps clarify things for you.

    • 0