Well i have the same problem, a legacy application is using 250 column in Ms-access without any problem, after migrating in .net we are stuck.
I have constructed the dataAdapter directly with code like that
Me.OleDbDataAdapterAPPA.UpdateCommand = Me.OleDbConnection1.CreateCommand()
Me.OleDbDataAdapterAPPA.InsertCommand = Me.OleDbConnection1.CreateCommand
With Me.OleDbDataAdapterAPPA.UpdateCommand
.CommandText += " update APPAREIL set "
'--- Pour chaque chaque paramètre ...
Dim i As Integer = 0
For Each dc As DataColumn In Me.DataSet21.Tables("EQ").Columns
Dim xc, xCarry As String
' xc = "PID"
If dc.DataType.Name = "String" Then
xc = dc.ColumnName
.CommandText += xCarry & "[" & xc & "]=? "
xCarry = ", "
.Parameters.Add(xc, OleDbType.Char, 0, xc)
End If
Next
.CommandText += " where CLEF_APPAREIL=? "
.Parameters.Add("CLEF_APPAREIL", OleDbType.Integer, 0, "CLEF_APPAREIL")
End With
but it seems that the Jet OleDb is limited to 128 columns whatever you try.
Before spliting the table in many narow tables in a one to one relationship i am looking for a way to fix that problem
regards
Loïc