Welcome ... HTH! :-)

What I do in the "of_stop" is set a Boolean ib_stop variable and then in my processing loops ...

For example:

FOR li_loop to li_max

IF ib_stop = TRUE THEN

ib_rc = -2 // Processing stopped

EXIT

else

// Processing here

END IF

NEXT

RETURN ib_rc

Regards ... Chris

Thanks Chris,



That is also what I do .. you need an Yield() in the loop to receive the signal to your ib_stop.

also you might consider THROW of a decendant exception instead og having to code a deep deep callstack return structure.



I just thought it would be so much easier if I could kill the thread instead of coding for the cancelation.



Do you know if ShareObjects are long term supported by Appeon and do you know it is is stable to use in serious applications ?



Thanks :-)

//Steen



ps. R3 Beta 2 ROCKS :-)

Hi Steen;

Good idea about using a Yield() in any thread's looping.

AFAIK, there are no plans to deprecate the SharedObject feature in Appeon PB. I have used this feature in many PB Apps and I also know of many PB shops that have Apps that use it. I also support this feature in my STD Framework. I have had a lot of people tell that they use it as well.

Yes, R3 Beta 2 is much further along feature / stability wise. :-)

Regards ... Chris

.