a lot of code and included files

[fiona]

I have a movieclip named ready, that onRelease I want some files to be included.
If the included files have a lot of code it doesn´t work, the button becomes inactive.
if the first included file has a lot of code and the counter=2 it doesn´t work. I assumed that the included files could have a lot of code because only one option is possible at time. I mean if counter=2, the option counter=1 is of no interest and it shouldn´t matter how much code counter1.as has.

ready.onRelease = function(){
if (counter==1 ){
#include "counter1.as"
}else if (counter==2 ){
#include "counter2.as"
}
}

First I tried to have all code in one frame without any included files but when that didn´t work I tried with the included files, now when that doesn´t work either, what to do if you have much code???
I have worked with this for a week now.

[lelales]

I haven't heard of this problem before. How many lines of code do you have? Maybe the code you are including or placing in the timeline isn't all correct and is causing the problems.

[fiona]

counter1.as

if (counterr==0){
#include "holder1_0.as"
}else if (counterr==1){
#include "h1_1.as"
}else if (counterr==2){
#include "h1_2.as"
}else if (counterr==3){
#include "h1_3.as"
}else if (counterr==4){
#include "h1_4.as"
}else if (counterr==5){
#include "h1_5.as"
}else if (counterr==6){
#include "h1_6.as"
}else if (counterr==7){
#include "h1_7.as"
}else if (counterr==8){
#include "h1_8.as"
}else if (counterr==9){
#include "h1_9.as"
}

counter2.as

if (counterr==0){
#include "h2_0.as"
}else if (counterr==1){
#include "h2_1.as"
}else if (counterr==2){
#include "h2_2.as"
}else if (counterr==3){
#include "h2_3.as"
}else if (counterr==4){
#include "h2_4.as"
}else if (counterr==5){
#include "h2_5.as"
}else if (counterr==6){
#include "h2_6.as"
}else if (counterr==7){
#include "h2_7.as"
}else if (counterr==8){
#include "h2_8.as"
}else if (counterr==9){
#include "h2_9.as"
}

for example h1_9 , one of the included included files, has over 400 lines
The file is to long to place here but i place the beginning of the file.

//--------------h1_9--------------
//--------------h1_9_1--------------
kvadrat.createEmptyMovieClip ("h1_9_1",1);
kvadrat.h1_9_1._alpha=0;
kvadrat.h1_9_1. lineStyle (1,0,100);
kvadrat.h1_9_1. beginFill (0xABCDEF, 105);

kvadrat.h1_9_1.moveTo (1,1)
kvadrat.h1_9_1.lineTo (kvadrat.col1._x-2,1);
kvadrat.h1_9_1.lineTo (kvadrat.col1._x-2,kvadrat.row1._y-2);
kvadrat.h1_9_1.lineTo (1, kvadrat.row1._y-2);
kvadrat.h1_9_1.endFill() ;
	
kvadrat.h1_9_1.onRelease = function(){
	
	
if (kvadrat.h1_9_1._alpha==0){
kvadrat.h1_9_1._alpha=100;
}else if (kvadrat.h1_9_1._alpha==100){
	kvadrat.h1_9_1._alpha=0;
}
}


//--------------h1_9_2--------------

kvadrat.createEmptyMovieClip ("h1_9_2",2);
kvadrat.h1_9_2._alpha=0;
kvadrat.h1_9_2. lineStyle (1,0,100);
kvadrat.h1_9_2. beginFill (0xABCDEF, 105);

//--------------/h1_9_20---------
//----------------and so on ------------------------
//--------------/h1_9---------

[FormerSwinger]

I've never used the include but I'm working on project with tens of thousands of line of code. So i seriously doubt that the amount of code is the issue here. Check your code for typos and infite loops (could be caused by methods calling each others as well as actual loops).

[jsebrech]

I've only had one problem with too much code. If classes get bigger than 32KB byte code, they no longer work correctly (mx 2004). You get a very specific error in that case though, so I seriously doubt you've run into that.

[flashead]

This is right in Flash Help:

Description
Compiler directive: includes the contents of the specified file, as if the commands in the file are part of the calling script. The #include directive is invoked at compile time.

Using #include is a 'compiler directive' meaning only the compiler pays attention to #include, so calling #inlcude at runtime probably isn't doing anything. Or if it is doing anything at all I'd hazard to guess that despite having those includes inside a function, they might be getting included anyway right away.

EDIT: I stand corrected. I just wanted to test this whole scenario out for myself to see what it would do. I never thought it would even work.
Nevertheless I'd keep all the code in one file, it'll be easier to deal with. As others have said, it's not because of too much code. It's likely just a code error.

I can't imagine what you could possibly be doing that warrents the need for THAT many .as files.
I know it's a little late, now that you've already written ALL that code, but here's a suggestion for future reference in regards to dynamic filenaming:

Rather than have dozens of if() statements to load a particular file based on a partucular variable's value, you can 'build' that filename using the variable and write only a few lines.

So instead of:

if (counterr==0){
#include "h2_0.as"
}else if (counterr==1){
#include "h2_1.as"
}else if (counterr==2){
#include "h2_2.as"
}else if (counterr==3){
#include "h2_3.as"
}

You end up with:

#include "hs_" + counterr + ".as" 

(Note this doesn't work with #inlcudes, I just used it as an example to illustrate dynamic paths):