Click here to Skip to main content
15,905,144 members

Comments by candice_Blav (Top 5 by date)

candice_Blav 4-May-11 22:57pm View    
Thanks for the solution Bryian Tan, I think the solution you gave me uses the registry. They don't want us to use that kind of method..

Right now i'm using
Private Declare Function SQLConfigDataSource Lib "ODBCCP32.DLL" (ByVal hwndParent As Integer, ByVal ByValfRequest As Integer, ByVal lpszDriver As String, ByVal lpszAttributes As String) As Integer
candice_Blav 4-May-11 22:54pm View    
@walterhevedeich
sorry for my vague question... i've improved my question. hope you'll help me.
candice_Blav 27-Apr-11 22:19pm View    
Deleted
I've been using the mouse for quite some time and I didn't know that the mouse has a triple click... :)
candice_Blav 20-Apr-11 5:46am View    
again, i think i found the suspect. If the DataGridView.AllowUserToAddRows is changed to false, that triggers the error. But when i removed the DataGridView.AllowUserToAddRows part, it went ok.
candice_Blav 19-Apr-11 21:22pm View    
Thanks for the solution, I tried to test this procedure to another project, but it went well. By the way, I found out something. It goes something like this :

I have a tabControl with 2 tab pages. Each tab has a datagridview. The datagridview in tab 2 is the one using the above procedure.

Situation 1 : When the form is loaded, tab 1 is being shown and no error was displayed but when you close the form after opening the form, the "ArgumentOutOfRangeException" shows.

Situation 2 : After the form is loaded, when you go to tab 2, and then close the form, no error shows.

Is it possible it's because the datagridview in tab 2 hasn't repainted?... I'm not sure of my theory but hope you can help me..

Hope you can help me.