Visual Basic Binding of ZOOM Z39.50 API

Logged In: YES
user_id=470665

We've released YAZ 1.8.9 with a fix for this. Please try it out

Logged In: YES
user_id=470665

We've released YAZ 1.8.9 with a fix for this. Please try it out

Logged In: YES
user_id=470665

I've verified this to be bug in ZOOM C YAZ. I'll be back
tomorrow.

-- Adam

Logged In: YES
user_id=470665

You've probably seen this, but here it is just in case you're not
reading the ZOOM mailing list. Looks like you've fallen for the
old
"cache associated with the record object" bug. Net::Z3950
used to do
that up till version 0.14 too!

Logged In: YES
user_id=470665

I've verified this to be a problem. The only workaround I can
offer at the
moment is to redo the search between changing the record
syntax or the
element set, such as in this VB snippet:

zconn.SetOption "preferredRecordSyntax", "SUTRS"
zconn.SetOption "elementSetName", "B"
Set zrs = zconn.Search(zq)
Set zr = zrs.GetRecord(0)
AppendText zr.GetRecordSyntax
AppendText zr.RawData

zconn.SetOption "preferredRecordSyntax",
"UNIMARC"
zconn.SetOption "elementSetName", "F"
Set zrs = zconn.Search(zq)
Set zr = zrs.GetRecord(0)
AppendText zr.GetRecordSyntax
AppendText zr.RawData

Note that contrary to the documentation, I am actually setting
the various
resultset options on the connection object. This seems to
work better, not
sure why.

Since all that VBZOOM does is put a wrapper on top of the
corresponding YAZ
ZOOM functions, I suspect that YAZ is doing some sort of
caching that isn't
getting properly purged or reset when recordSyntax or
elementset options are
changed. Although, this could very well be a function of my
use (or misuse)
of the YAZ ZOOM functions. Are there any YAZers out there
who could
comment?

I'll look into this more for the next release.