@deanwenick
10 years ago
thanks for tracking that down. I had the same problem until I downgraded to NextGen 2.0.40
thanks