>>No it's not fixed in SP1 because MS doesn't consider it a bug.
>
>:)
>
>I was wondering if something not considered a bug might have been enhanced. And, also, I was wondering if all that is indicated as fixed is the only thing that was touched.

The application I rolled back to VFP7 was generating this error in VFP8SP1.