Results 1 to 3 of 3

Thread: [2008] DatagridView Cell keypress

  1. #1

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    [2008] DatagridView Cell keypress

    is there a way to catch keypress event in DataGridView Cells ?

    i want to catch event when user press tab, if user move to another column using mouse..it won't be catch

    any idea?

    thanks,

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

  2. #2
    Hyperactive Member mrmojorisin's Avatar
    Join Date
    Oct 2007
    Location
    London Town Vocation: Garden Cricket Genuis
    Posts
    439

    Re: [2008] DatagridView Cell keypress

    Im not sure i completely understand you but this may help.
    This will stop the user from being able to tab cells in your datagridview using the tab key:
    vb Code:
    1. Private Sub DataGridView1_KeyDown(ByVal sender As System.Object, ByVal e As System.Windows.Forms.KeyEventArgs) Handles DataGridView1.KeyDown
    2.         If e.KeyCode = Keys.Tab Then
    3.  
    4.             e.SuppressKeyPress = True
    5.      End If
    6. End Sub

    Let us know if this is what you wanted!

  3. #3

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    Re: [2008] DatagridView Cell keypress

    thanks mrmojorisin

    This will stop the user from being able to tab cells in your datagridview using the tab key: -> hm, not exactly what i mean..

    i mean if user press Tab in the Cell..it will prompt an action otherwise it will prompt nothing

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width