PDA

View Full Version : Character Limit in HTML Tables


cowdogman
March 2, 2007, 00:47:56
Hi:

For purpose of speed in loading a large table into a TextControl, I'm preparing a code generated HTML table which I then load into a TextControl. Works great and it's fast but I notice that if the text characters in a table cell are greater than some number (I haven't counted but I'm guessing around 300 or 400 characters), I get the error quoted below. The error occurs at the following line of code where I load the completed table:

TextControl1.Load(strTable, TXTextControl.StringStreamType.HTMLFormat)

"strTable" is a string with the HTML for the table.

As I said, works great except when the text in a cell is "too long."

Is there some character/cell height limit (expanding the width of the TextControl didn't help)? What else could it be? Is there a LoadSetting I need to set?

Any thoughts would be appreciated.

I'm using Version 13 of TextControl.net in VS 2005.

Brad

"System.Exception was unhandled
Message="The operation could not be performed. An unexpected error has occurred.
(01-1D09)"
Source="TXTextControl"
StackTrace:
at TXTextControl.LoadSettings.LoadFromString(String strData, StringStreamType iStreamType, TextControlCore tx, Boolean bSelection)
at TXTextControl.TextControl.Load(String stringData, StringStreamType stringStreamType)
at HTML_Table.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallba ck(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchM essageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.UnsafeNativeMethods.IMsoCompo nentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.Run MessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.Run MessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationCo ntext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase.Run(String[] commandLine)
at HTML_Table.My.MyApplication.Main(String[] Args)
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()"

cowdogman
March 2, 2007, 05:13:48
In working on this issue some more, I've come to the conclusion that the problem is the size of the table, not the size of any cell. I've seen various posts in the forum regarding errors when loading large html tables. Is there a solution to this problem other than breaking the large table into a series of smaller tables?

Thanks.

Brad

Gunnar Giffey
March 2, 2007, 15:19:50
Hi Brad,

Yes, tables do have a character limit and we recommend not to span tables over more than 2 pages. The exact limit depends on various factors, e.g. formatting, images, etc., thus it is no possible to give you a number.

Another solution apart from using more than one table is not available, sorry.