>Nice function.

yup. Small difference in my "design":
I have a standard line with stack level, line number a method/function name
(numeric first because they form small columns) and optionally add the other lines (indented)
depending on the app or user.
So for each row in laStack a special writer-function is called,
which draws on a very small pool of other "formating" functions.
All they need is laStack and row number.
Since row numbers a not to large and this is mostly used in error situations,
there is no worry for a bunch of 1 line functions making the program slow ;-)

Especially the line number makes my life easier.
And if the error handler shows you the "real" source lines
quite often it is not necessary to recreate the error in the debugger,
because the thinking error of the programmers part is evident enough.
So I can start bonging my head on the desk as I start vfp to fix the error.

Productivity is greatly enhanced!

regards

thomas