>Hi Craig,
>
>>Thinking about this, it could be a resource issue...since CR 10 is the current version, it was fixed first and then released. Just a guess on my part.
>
>Nope, the release version of CR 10 had the same problem. It was fixed in a later patch. There is some Kb out there, but could not find it quick enough.
>
>Walter,
>
>

I understand that. My point was they fixed it in a CR10 SP before a CR9 SP because 10 is the current release.