>>However, passing twelve (!!) seems a bit out. Surely you can massage the
data into a local record and pass that. It makes for easier and more flexible
code. Personally, i am trying to go for only 2 params maximum, except for
toolbox calls which don't let us decide.<<

Massage the data, hmm, that sets up some _very_ weird mental images. But
y'know what this makes me think of? Packing & moving. (When you've made five
long-distance moves in seven years, this is an analogy that comes all too
readily to mind.) That is, if I'm just moving down the street or across the
hall, I'll gladly carry dozens of boxes back & forth rather than go through
the excruciating horror of having to pack & unpack everything properly, even
though by this time I'm quite good at it. It's only if I'm moving a long
distance, or if my stuff is going to spend some time in storage along the way,
that I force myself to Do It Right.

On to a completely unrelated question (just not important enough to merit a
fresh subject header). I was doing some stuff with rgnBbox'es, and it didn't
work. Finally pinned it down to a simple typo:
  temprgn&.rgnBbox.left% (one dot)
by mistake for
  temprgn&..rgnBbox.left% (two dots)
No errors, it just didn't do anything. (Obvious disclaimer: no errors _visible
to the naked eye_ --for all I know, it was overwriting a huge chunk of memory
that the app happened not to be using just then.) But I'm curious-- does
anyone know what FB or the compiled app _thought_ it was doing when it
encountered that single dot?