I was 100% certain, but I went back and checked this and you're right - too much late night editing!
This solves the mystery, because Job 0 cannot be removed. However, on the plus side, this problem actually allowed me to develop a tidier method of managing the spawned jobs. Many thanks for your insight! -----Original Message----- From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-boun...@lists.q-v-d.com] On Behalf Of Marcel Kilgus Sent: 30 January 2011 21:33 To: ql-us...@q-v-d.com Subject: Re: [Ql-Users] Help! Reasons for MT.FRJOB Failing Adrian Ives wrote: > No, it isn't. me is defined as -1, for the current job. Have you checked that in an actual disassembly or in a debugger or just had a look at the source? Marcel _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
