Jim wrote:
>My guess is you're running into the onlyLatestVers bug fix. David Fedor
>sums up the difference in behaviour rather nicely:
>
> "In 3.0 and earlier, setting this flag while providing both
> a type and creator id could return you multiple databases
> (if there were in fact multiple with that type/creator
> combination). In 3.1, you'll only get one database which
> has the given type and creator... it'll be the database
> with the highest version number which matches the criteria."
>
>Does this sound like the problem?
That's it! In my case, all the databases have the same type, creator, AND
version number, differing only in name (and in such a case, I'd expect the
function to keep getting the "next" such database -- but apparently it does
not do so). I do indeed have that parameter set to true. I haven't tested
it yet, but this sounds like it must be the problem.
Thanks a ton!
Cheers,
-- Joe
,------------------------------------------------------------------.
| Joseph J. Strout Biocomputing -- The Salk Institute |
| [EMAIL PROTECTED] http://www.strout.net |
`------------------------------------------------------------------'