On Tuesday 27 May 2008 12:17 pm, Paul McNett wrote: > Adrian Klaver wrote: > > -------------- Original message ---------------------- > > From: Ed Leafe <[EMAIL PROTECTED]> > > > >> On May 27, 2008, at 2:30 PM, Adrian Klaver wrote: > >>> I may be reinventing the wheel here, but I could find no method in > >>> dGrid to find the column index for a column by using its DataField > >>> name. getColByDataField() returns a column name but no index value. > >>> The problem lies in using setValue() where a row and column index > >>> are needed. To get around this I modified getColByDataField(): > >> > >> Columns have a property named '_GridColumnIndex'. It was created for > >> "internal use only", hence the leading underscore. > >> > >> Question: why, if you have a column reference, do you need the index? > > > > As far as I can tell the only way to set a value in a dGrid is to use > > dGrid.setValue(row,col,val) where row and col are index values. > > This is actually surprising to me, as I never use setValue() to set > values in a grid. I set the value in the underlying bizobj or dataset, > and refresh the grid. > > Paul
I am starting to work on the idea I brought up in: http://leafe.com/archives/showMsg/383757 an incremental search on a column.ListEditorChoices. The choices are created from a query on a lookup table but they are 'attached' to a specific column. My initial efforts have been from the perspective of the dGrid.col supplying values to the DataField. This is why I have been working from the dGrid down not the bizobj up. -- Adrian Klaver [EMAIL PROTECTED] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
