Quote:
Originally Posted by DoctorOhh
What you said you were using above was 5.31 which introduced the error. The error was recognized relatively quickly and 5.31.1 was released to correct the issue.
You're welcome, I'm glad things are working for you again.
|
Oops your right, I miss read it when I wrote it. I was using 5.31