Dynamic MSSQL results, DataGridViews and changes

[David Costello]

Hello everyone,
It would appear I'm trying to do something that's completely undocumented. I can't find anything of any use online to help me with this...

I'm working on developing an MSSQL query editor for a bigger database program, for a university project. The project consists of around 50 or so tables. The query editor is meant to display a tabcontrol with a text box for query input on each tab, and a Datagridview, to display the resultset from the query(s).
Multiple tabs allow the user to compare the results of two or more queries (I have 5 tabs, and 5 datagridviews for the 5 textboxes on those tabs).

I'm having issues when it comes to saving new rows added to the resultset displayed in my datagridview. If I select a table that contains a primary key, the primary key information is lost, so when I save the changes made in the datagridview, I get exceptions about my primary key field being read only.

The problem would be a lot simpler if I was doing constant queries, but becauss the program must be able to execute any query the user gives it, it needs to be able to understand if a field in the resultset is a primary key.

Hopefully I've explained my problem cleary. Suggestions/Ideas anyone? They'd be most appreciated. :)

[kenobewan]

Tricky problem - there are two parts as far as I can see - error handling and ensuring that the datagridview is updated so that the primary key does not generate an error.

You could modify this for the error handling:

Sub GridViewUpdated(ByVal s As Object, ByVal e As GridViewUpdatedEventArgs)
        If Not e.Exception Is Nothing Then
            lblError.Text = "Could not update row"
            e.ExceptionHandled = True
        End If
    End Sub

For the updating are you displaying the primary key in the datagridview? It should be ready only so that it can't be changed. If you are trying to set the primary key in the update instead of using it in the where... Please provide more details re this.