No kidding, Paul? Since my early days as a scripter (1 year ago), I've been
omitting the "return" syntax when I didn't need to explicitly return true or
false. Have the results really been coerced this whole time? I'd better do
some research into this.
Anywho, I appreciate your suggestion and just tried adding the "return txt"
step to the RelatedRequest() handler. Same results...it works when there's
less than 32K, doesn't work at any larger size. Downright peculiar, I say.
There must be something simple I'm missing...when I have time on Friday,
I'll do some in-depth testing. If I come across something astonishing, I'll
post it to the list...
Thanks again, Paul. You're always there for me!
Jed
On 5/9/01 12:56 PM, you wanted me to know this:
> On 5/9/01 11:27 AM, "Jed Verity" <[EMAIL PROTECTED]> wrote:
>
>> Update: I've tried this on two other machines and it works fine on one (the
>> G3 bronze laptop) and errors on the other (beige G3). Still searching for
>> the reason (all machines have 9.1, AS 1.6, and Smile)...
>> Jed
>
> In that case, there may be a coercion supplied by an osax on the machine
> that works. Did you try my suggestion about returning 'txt' as the parameter
> to use in Maillt()? What you were doing with the other handler as parameter
> wasn't right without, at least, not without 'return txt' as its final line,
> and it might have been coerced to what you want by an osax not present in
> the other two machines.
>
> Another possibility would be the amount of RAM dedicated to Entourage. But
> then, I'd expect a different error message than the one you got.
~)~)~)~)~)~)~)~)~)~)~)~)~)
Jed Verity
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
