That fixed it! ThanksDave
Hi Dave,this error was fixed in r3041. It was introduced as part of some adaptions for the db_berkeley module. Please update to a recent trunk version, and reportif you still have issues.Cheers,Henning