Does IIS6 limit an asp page's vb script number of variables used?

[POSAPAY]

I'm getting this error:

Microsoft VBScript runtime error '800a0006'

Overflow: '[number: 32771]'

/default.asp, line 519

if I get rid of a variable completely in my script, it seems to decrement by one.
I don't have any integer variables, they are all strings, so I'm wondering what number or variable is overflowing here.

Is there a control for the scripts?

(BTW, the script is a pretty darn complex, large script, with many asp pages linked together using #includes, and the line 519 is actually past many thousand lines processed prior to it.)

Any ideas anyone?

 

[POSAPAY]

From a Microsoft IIS forum I got a response where they mentioned: "VBScript uses a signed INT to enumerate variables, which suggests that the maximum number of variables will be 32767"

But after a bit more testing, my conclusion is that the variable that is a signed INT overflowing is actually counting executable lines.

Alternatly, it could be counting jumping in and out of code. For example having HTML code and then jumping into serverbased VBScript code and back to HTML code.

I still haven't found documentation on this, and would love to see whitepaper saying these limitations.

So my solution will be to replace sharp includes of asp pages in select statement with a request redirect to that page and adding headers and footers on that, to avoid too many lines of code to be in a single page load.