Event Editor space (OpenInsight 32-bit Specific)
At 31 JUL 2002 09:30:07AM Colin Rule wrote:
I though going to 32 bit would remove the space limitations.
In the event editor there is still a limit, eg I cannot type anymore at about 800 lines of code.
I have to remove stuff and put it in an INSERT to get over this, which makes debug a real P.I.T.A.
Colin
At 31 JUL 2002 09:38AM Oystein Reigem wrote:
Colin,
I agree it's a PITA, and no matter what some say about structuring the code and using subroutines/functions there are always cases where long procedures should be allowed!
- Oystein -
At 31 JUL 2002 09:40AM [url=http://www.revsoft.co.uk" onMouseOver=window.status= Click here to visit our web site?';return(true)]Revelation Software EMEA Support[/url] wrote:
32 bit removes the variable and row limits however regretfully it does not remove specific Windows control limits as these are outwith our control. We will see what can be done (if anything) about this.
At 31 JUL 2002 11:07AM Mike Ruane wrote:
Colin-
What workstation OS?
Thanks-
Mike Ruane
At 31 JUL 2002 11:45AM Colin Rule wrote:
Mike,
I am using Win 98 Rev 2.
I will be changed to XP soon though.
At 01 AUG 2002 10:08AM [url=http://www.revsoft.co.uk" onMouseOver=window.status= Click here to visit our web site?';return(true)]Revelation Software EMEA Support[/url] wrote:
Due to Win 98 restrictions this cannot be increased on this OS.
At 26 NOV 2002 06:24AM Rich Channer wrote:
Does this rule also apply to the system editor? I just added a bit of code to a proc 1100 lines long, and no error was generated. However, when I re-opend the proc, the last few lines had been lost off the end…
I too am using Win98se
Richard
At 26 NOV 2002 11:08AM Donald Bakke wrote:
Richard,
What you are seeing is a different problem that what is being addressed in this thread. You are getting code that appears chopped off because the Windows control used can only display so many characters, i.e. this is not a problem of storing that much text in the record nor is it necessarily the problem of compiling object code that is reaching the threshold.
In your situation people have had mixed results by upgrading to Win2000 or WinXP. Another "technique" that sometimes works is to add several rows of astericks at the bottom of your stored procedure.
Your final solution may have to be to abbreviate your code whereever possible, but you knew that already.
