this bug was on of the first thing MS fixed when they started working n
5.0a (AFAIK anyway (s))
Arnon
> Actually, you are right. One of the developers in our group was working
on
> this problem and he said just the other day that he still had the problem
> with 5.0a. Turns out he really didn't and hadn't yet tested with 5.0a.
>
> Bob
>
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only