Hi, there has been a bug reported concenring to this issue:
See post in the forums, and solution there also:
However, the sql 1.7 to 1.8 update script need to be
fixed ( I can't do that myself).
I hope it can be fixed before the new 1.8.5 release is out.
Thanks all for your work. :-)
Log in to post a comment.