This goes in line with something I learned after submitting a bug for BASE64 ENCODE. The formula was changed so there was one very, very long line of code for large amounts of data. This drawing for this line suddenly stopped after something like 37K characters. It turns out Windows has a visual limit on what it will try and display. We hit the horizontal visual limit, and I suspect that you may be hitting the vertical limit. While the text may not be displayed, I do believe that the text in its entirety is present, thus the successful Length checks that were done. As another post noted, the more they scrolled, the slower the window got. This is probably why a limit on what is drawn is done so the system can remain responsive.
Perhaps a List Box could be used instead, 1 row per SQL statement? Or every 10 statements depending on responsiveness? -- View this message in context: http://4d.1045681.n5.nabble.com/Character-limit-in-form-text-variables-tp5750252p5750268.html Sent from the 4D Tech mailing list archive at Nabble.com. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
