Problem selecting multiple rows in windows datagrid with shift-click

I have a datagrid on a windows form in a vb.net application. When I run it either in debug mode or from a build on my developer machine (winXP) I have no problem.
But when my users run it (both on XP also) from the build installed on their boxes, they experience the following:
1. when datagrid first loads, select the first row.
2. scroll down to some point farther in the list, so that the first, selected row is no longer visible in the grid (but is still selected, of course).
3. holding the shoft key, click any row to attempt to select all rows from the beginning to the clicked row.
4. instead of the desired result, just the shift-clicked row is selected.
5. HOWEVER, if the user then clicks in a cell of the datagrid (any cell, it doesn't seem to matter), then repeats the step, the mutiple selection now works.
6. Note that if the first row is still visible, then there is no problem - only a problem when all painted rows are unselected.

Unfortunately, as I said, on my dev machine this never happens - shift-select always works as expected.


Thanks for helping...
Ian


irashkinAsked:
Who is Participating?
 
andrewharrisConnect With a Mentor Commented:
I would check to see what version of the framework they have installed. There was possibly a bug that was fix or introduced.

Andrew
0
 
irashkinAuthor Commented:
sorry, forgot to mention that I did check and we are all running 1.1.4322.

good call though.
0
 
andrewharrisCommented:
Is it only one other machine? I have seen "similar" issues with cheap low memory video cards.

Andrew
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
irashkinAuthor Commented:
good question.
they're all dell boxes, but with various graphics cards.
the working one (mine) is an intel adapter, with 64 mb
the two buggy ones are a different intel adapter with only 48 mb, and an NVidia with 64 MB.
I will have to try it on another - maybe one of the others in my office has the same as me for an accurate comparison.
I'm doubtful, but will pursue - thanks for the tip.
0
 
irashkinAuthor Commented:
I found another computer to test on, very similar to mine.
My graphics card is a Intel(R) 82845G/GL/GE/PE/GV with 64MB; this new one is a Intel(R) 82845G with 64 MB.
As with the others, buggy on this computer, still only works properly on mine.

Any further ideas?
thanks,
ian
0
 
irashkinAuthor Commented:
Today I discovered the solution!
.Net framwework SP1 fixed this bug!!! Microsoft made no mention that I can find of this bug, but turns out the SP does fix it, so there you go.
cheers, and thanks to andrewharris for trying.
Ian
0
 
andrewharrisCommented:
Comment from andrewharris
Date: 10/30/2004 09:27AM EST
 Your Comment  


I would check to see what version of the framework they have installed. There was possibly a bug that was fix or introduced.

Andrew
0
All Courses

From novice to tech pro — start learning today.