Hugo

I leave the space so the func's arrgs stand out (and indeed where the func name ends, not mistaken for a C, for instance)

Well-aligned, tabbed code is so much easier to follow, esp keeping all the "="s in 1 column. Yours looks neat and readable. Reminds me a bit to much of C though :-)

Real estate? If you have to indent nested code too far, if you face North, it'll end up in Ontario! :-)
>Terry,
>
>I try to write the code pretty much like you, except I do not leave spaces between function's parenthesis and the parameter (like in ABS( lnSchemTot1)), but what I really write different is the insert command, I would write your's like this:
>
>

>Insert Into RZSTOP ;
>		( ;
>			Rte_No, ;
>			Rte_Let, ;
>			Directn, ;
>			Number, ;
>			Zone, ;
>			Stop, ;
>			County, ;
>                	Flags, ;
>			SeqNo ;
>		) ;
>	Values ;
>		( ;
>			lcRoute,  ;
>			lcGen, ;
>			lcDirectn, ;
>			I, ;
>			VAL(.aReorderStops( I, 1)), ;
>			.aReorderStops( I, 3), ;
>			.aReorderStops( I, 6),  ;
>			lcFlag, ;
>			1 ;
>		)
>
>

>
>I know it uses lot of real state, but I like it <g>