07-11-2025, 06:56 PM
Without the code, I don't think anyone is going to be able to help you. File size is seldom an issue (I don't know what the limits are, but I've certainly compiled files much larger than 5mb in the past.)
Is the code using too much compiler stack space? Too many variable names? Too many nested IFs? Too many sub/function calls without proper returns? Is it getting bogged up trying to optimize or unravel structures?
Without the code, who knows! The issue could be any countless little things, or internal limitations.
At this point, all you can do is:
1) Share the code and hope someone has time and is nice enough to check it all out for you to try and dig into the problem. Usually our dev team is pretty happy to do this as we're curious folks ourselves and like to know what they of odd limit someone found -- but it's the middle of summer and everyone is busy with lifeing.... a 5mb bas file isn't nothing small to sneeze at, and that's asking a lot of anyone to sir down and take a look at it after a hot grueling day out in the 90+ degree sunlight.
OR
2) Strip out segments of code, say 1000 lines at a time until it compiles. When you find it WILL compile again, add in the other code *except* that last 1000 lines. If it still keeps compiling after that, then you know whatever the issue is, it's in the flow of those 1000 times. Add them back in 100 lines at a time until you can pinpoint the issue. Once found/zoomed in on in such a manner, finally fix the issue yourself.
Is the code using too much compiler stack space? Too many variable names? Too many nested IFs? Too many sub/function calls without proper returns? Is it getting bogged up trying to optimize or unravel structures?
Without the code, who knows! The issue could be any countless little things, or internal limitations.
At this point, all you can do is:
1) Share the code and hope someone has time and is nice enough to check it all out for you to try and dig into the problem. Usually our dev team is pretty happy to do this as we're curious folks ourselves and like to know what they of odd limit someone found -- but it's the middle of summer and everyone is busy with lifeing.... a 5mb bas file isn't nothing small to sneeze at, and that's asking a lot of anyone to sir down and take a look at it after a hot grueling day out in the 90+ degree sunlight.
OR
2) Strip out segments of code, say 1000 lines at a time until it compiles. When you find it WILL compile again, add in the other code *except* that last 1000 lines. If it still keeps compiling after that, then you know whatever the issue is, it's in the flow of those 1000 times. Add them back in 100 lines at a time until you can pinpoint the issue. Once found/zoomed in on in such a manner, finally fix the issue yourself.