Before you post an error number thread;

**sekasi** · November 9th, 2008, 04:10 PM

Go into your fla settings, check the box called "allow debugging".

Re-compile.

This time around you'll get the actual row number of the faulty code. Much easier for you to troubleshoot, not to mention the people trying to help here.

Oh, uncheck it before you publish anything online since it has a few security related issues.

**TheCanadian** · December 11th, 2008, 12:35 AM

Also look for your error code in the LiveDocs; they explain a lot of them in detail.

Compiler Errors
Compiler Warnings
Run-Time Errors

Senocular has some good information, as usual:
Flash Player Runtime Errors and How to Fix Them
Flash Player Compiler Errors and How to Fix Them

**ayumilove** · January 8th, 2009, 08:17 AM

thanks canadianguy for the 3 extra links. its very useful

**Felixz** · January 18th, 2009, 02:52 AM

You can also use shortcut: Ctrl + Shift + Enter

**foxbat** · July 1st, 2009, 11:45 AM

#2044 error? read this: http://www.adobe.com/devnet/flash/qu...ta_cue_points/

**jgomula** · September 17th, 2009, 12:03 AM

Thank you!! Didn't know about the debugging option - knowing the line number certainly helps!

**Dizquard** · November 3rd, 2009, 07:01 AM

I can strongly recommend the good Mr Curtis Morley http://curtismorley.com/flash-9-flex-error-messages/
He explains a lot of the most common errors in details.

**grass** · November 5th, 2009, 11:03 AM

can I just say...

is there a cool way to check whats wrong (without 10s oh hrs of testing random things + forum), when:

1. compiler says "total 2-9 errors reported", lists none... and while you start de-attaching your classes one by one (with no reference to them available at all), the error count raises... till everything's detached and it tells you "9 errors reported"?
- this fix caused me ~10hrz

2. if the row-number chooses a random row (usually empty or commented out one), and if you delete this or any other row, it just chooses random new one... (usually empty or commented out one) ?

3. the compiler sort-of ignores the mistakes, you might make with instancenames... is there an actual cool way to check if it has ! problems with ... u know, stuff in da .fla file... or is it a class?

anyone willing to meditate on those f10 issues (plz don't move to compiler forum, it's usually lame!!!), i can give a reward (which is dnx, if you don't live in the same town)

PS: oh yeah 1 more:

4. what's with the library item's attaching? you know if you try to do pretty much whatever with those "custom classes", the compiler disagrees all the time with non-sence explanations???

**JackD** · April 7th, 2011, 07:29 AM

The built in debuffer for Flash is awesome, the amount of times its saved me work. I mean compared to other scripting languages where the debugging as harder due to lack of feedback.

**Krilnon** · June 14th, 2011, 11:45 AM

Maybe people never find the line number because it's cut off by default. I just reinstalled CS4, and noticed this:

Maybe it's the different in CS3 or CS5… but I'm not about to reinstall to find out.

**SticksStones** · June 22nd, 2011, 07:00 AM

omg wtf...there is a "allow debugging" option! Oh, how i have called flash lots of nasty names! Sorry flash, my mistake, until now nobody had ever told me!

.....all the hours, all the frustrating days I've wasted just trying to find the problem!

Thanks, so so much!