Re: Programmatically determine number of parms inprocedureprototype?

Bob Cozzi wrote:
> 
> NEVER ADD PARMS BEFORE EXISTING PARMS in a procedure. All your existing code
> would then need to be recompiled. Of course if it is a local proc used only
> by one program, then that's a different story. But still... that's a very
> bad "standard".

"NEVER ADD PARMS BEFORE EXISTING PARMS" is a great rule.  But even for a
local procedure, inserting parms can lead to trouble if the data types
of the parameters are such that an unmodified or incorrectly modified
call would pass the compile.  For instance, say the procedure previously
had two numeric parameters and you insert a new second numeric
parameter; if you incorrectly add the new parameter at the end for one
of the existing calls, you now have a bug.  If the parameters have
similar ranges of reasonable values, you may have a bug that you will
never detect.  (It's always possible to have this type of bug even when
you aren't changing the number of parameters, but inserting parameters
dramatically increases the potential.)