hmm.. now that I realize this is just a wrapper package, the bug makes less sense. Perhaps one of the backend packages got upgraded recently, fixing this issue? Will continue to look into it and follow up with results. -- dann frazier