[AccessD] Learning .Net -- PHP Instead?

Yup. Over the years I have learned to accept this wisdom: each procedure or
function should have exactly one exit point. Define the result variable and
set it within your case statement, then jump out and return the result
variable. No headaches or scratched foreheads that way.
A.

On Wed, Jun 24, 2009 at 10:35 AM, Charlotte Foust <
cfoust at infostatsystems.com> wrote:

> Structured programming suggests you instead design the code so there is
> no reason to use a GOTO.  If you hit a condition in a particular branch,
> the code naturally arrives at the exitpoint.  Very clean concept, that.
>
> Charlotte Foust
>
>