.NET Framework - Too many fields problem

Asked By John on 11-Nov-08 08:58 PM
Hi

I have created a drag and drop form in vs 2008 using a single table from an
access backend database. When I run the app and press save on
BindingSourceNavigator I get the below error on line
Me.TableAdapterManager.UpdateAll(Me.MyDataSet). What is the problem and how
can I fix it? This table is working fine when used with an access front end
db app.

Thanks

Regards


System.Data.OleDb.OleDbException was unhandled
ErrorCode=-2147467259
Message="Too many fields defined."
Source="Microsoft JET Database Engine"
StackTrace:
at
WindowsApplication1.Events_DataDataSetTableAdapters.TableAdapterManager.UpdateAll(Events_DataDataSet
dataSet) in
C:\WindowsApplication14\WindowsApplication14\Events_DataDataSet.Designer.vb:line
15838
at
WindowsApplication1.Form1.StaffBindingNavigatorSaveItem_Click(Object sender,
EventArgs e) in C:\WindowsApplication14\WindowsApplication14\Form1.vb:line 6
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key,
EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs
e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e,
ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at
System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&
m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG&
msg)
at
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32
dwComponentID, Int32 reason, Int32 pvLoopData)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationContext context)
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[]
commandLine)
at WindowsApplication1.My.MyApplication.Main(String[] Args) in
17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[]
args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:




Paul Clement replied on 12-Nov-08 01:08 PM
¤ Hi
¤
¤ I have created a drag and drop form in vs 2008 using a single table from an
¤ access backend database. When I run the app and press save on
¤ BindingSourceNavigator I get the below error on line
¤ Me.TableAdapterManager.UpdateAll(Me.MyDataSet). What is the problem and how
¤ can I fix it? This table is working fine when used with an access front end
¤ db app.
¤
¤ Thanks
¤
¤ Regards
¤
¤
¤ System.Data.OleDb.OleDbException was unhandled
¤   ErrorCode=-2147467259
¤   Message="Too many fields defined."
¤   Source="Microsoft JET Database Engine"
¤   StackTrace:
¤        at

Sounds like there are too many columns in the Update query. This will occur when the number of
columns exceeds 127 in an Access database.


Paul
~~~~
Microsoft MVP (Visual Basic)
John replied on 12-Nov-08 10:11 PM
Any way round or solution for it?

Thanks

Regards
Paul Clement replied on 13-Nov-08 02:35 PM
¤ Any way round or solution for it?
¤

I'm afraid the only solution would be to split up your table into multiple tables. That's an awful
lot of columns for a single table.


Paul
~~~~
Microsoft MVP (Visual Basic)