Responding to tedd, R.C. wrote:

>  >rc:
>  >
>  >How about a url with a complete working version? This fix numerous
>  >errors thing is tedious and I'm lazy.
>  >
>  >tedd
>  >--
>  >http://sperling.com
>
>Don't be lazy.
>
>Takes all of 2 minutes to fix...start at the bottom, work your way up.
>Mostly it's wrapped comments that are the show stoppers.


First: This is a great demo! Thanks Robert.

Second: tedd, I'm not sure whether or not you're trying to run it 
from it in copy and pasted form from the Associate server, or copied 
directly from the e-mail version.  The Associate server version-- 
which I fixed-- lost all the constant underscores (and there were a 
bunch of them). Took me about six minutes to fix between BBEdit, 
where I fixed the obvious, and in the Editor, which caught the rest. 
Also, be sure you turn off "Toolboxes require 'Call"' in the 
preferences.

Now for a slight divergence:

I know there is a movement underway here to write all code in lower 
case like is done in some languages, but here is a good reason I 
prefer to see the reserved FB^3 words remain capitalized as they 
appear with the default settings in the Editor:

Without the  "Toolboxes require 'Call"' turned off in the preferences,

setrect( myRect )

could, at first glance, be confused with a standard array whereas,

SETRECT( myRect)

at least gives a hint that this is FB^3 syntax, particularly if 
"Call" is turned on (which is the default) and the word is not 
highlighted in the Editor.

Experienced coders may scoff at this, but for a newbie it can be very 
confusing.

Of course, it could be worse.

In M$ VB:

doMyStuff( rightNow )

could refer to a private function, a public function, a sub, a 
procedure or an array, depending on the context.

Although it would be much easier to forsake caps for lowers when 
coding, in my posts here I personally will attempt to continue using 
FB^3 reserved syntax in caps-- as is the style of the Reference 
manual-- for sake of clarity, particularly for newbies. Of course, if 
the foolishness of my ways is exposed, perhaps I could be convinced 
otherwise

Thanks again for the great demo, Robert.

Best,

Ken