APEX 4.0.1: restriction on maximum number of dynamic actions on a page?

Question

Hello,
I would like to know if there is a restriction on the number of dynamic actions on a page.
I have a page with 29 dynamic actions. All works fine on the page.
If I create another dynamic action that only display an alert or does anything else, I have the error message HTTP 404 when I try do display the page.
If I delete an old dynamic action and create a new one then the page works fine.
So after several tests, it seems that there is a maximum number of DA on a page but can someone confirm that?
Environment:
APEX 4.0.1
Embedded PL/SQL Gateway
Regards,
Sddc

Answer 1

I stand corrected in that some limits are acknowledged:
http://download.oracle.com/docs/cd/E17556_01/doc/user.40/e15517/limits.htm
Where are people getting these ideas that normal form or "Codd" said that there was a
limit on columns and if you had more columns than a database product found convenient to implement that it was a 'design defect'? I took database management as an undergrad and in grad school and there was NO rule about number of columns. Anyone who says there is is shoveling pure bs. Even if there were such a rule, and there isn't, it is very inadvisable for a vendor who allows 1000 columns in a table in their database product to impose a limit that is 1/10 of that in an interface to their database. (And btw you can create a table (A 'wide' table, in sqlserver with 30,000 columns according to this:
http://msdn.microsoft.com/en-us/library/ms143432.aspx )
Artificially dividing up data instruments that were administered/collected at one time into pieces in separate tables, just to make a vendor's developers' life easier and more convenient, or just to keep the product from competing with the extremely extremely expensive "enterprise" products the vendor sells, is not acceptable.
Splitting highly related data into separate tables for no reason other than the
interface is not capable of handling it, creates a load of problems that would not otherwise
exist. What if the user enters less than all the parts? Then someone has to figure out if the parts not entered had no data recorded in the source or if they were simply accidentally skipped. Basically someone or a program would have to enter those pages and denote they had no content if that were the case. Much more logic, much more opportunity for error vs keeping data that was highly associated together.
A software vendor can apply whatever limits they want and no one can stop them, that's for sure. But what would be better here is making these more clear up front. This is a "rad" development tool for very small and not hugely complex forms and reports. Be clear and there will not be people royally steamed over spending their time and money evaluating a product that is not designed to do much of what people need it to do. This stuff should be in an FAQ and the top of the forum.