Jason,

> I've fixed a couple issues and released a new version.
>
> This release should resolve Thomas's issue calls to Locate() generating a
> fetch from the server looking for a record that it couldn't find. Thomas
> wanted the Locate() method to not bother checking on the server if all of
> the records were already fetched into the client buffers. I decided this
> would be a good thing and made it default to not check the server but if you
> still want the old behavior you can add the lopCheckOnServer option in the
> call to Locate() if you want it to make sure.

Great! Will reduce network traffic a lot and give me in-memory locates
for an entirely fetched result set.

I haven't looked into detail, but is the behaviour also dependend on the
transaction isolation level as we have discussed via Skype?


Thanks,
Thomas