I have found that the bug begins as of 5.3.29 and is present in all
versions up to the latest 5.4.0-rc1.

Shane

>Hi Michael,
>
> I had actually thought of doing the same thing so I got as far as
>downloading 
>the different versions and I will go through them tonight and 
>let you know
>which
>version the error shows up in.
>
>cheers
>Shane
>
>>Shane, perhaps you could step through the versions between
>>5.3.27 and 5.4.0-rc1 one at a time, until you find the version
>>that causes the problem? This is assist us in tracking down the bug.
>>
>>Michael.
>>
>>
>
>

Reply via email to