This problem went away when I switched from the bdb backend to the ldbm backend (still using DB 4.1.25 though). Tim