Millennium Cataloging "freezing"

["Wing, Robert" <robert.wing@xxxxxxxxxx>]

We have just started using Millennium Cataloging, but I don't think our
inexperience is the cause of our problem.
What we are trying to do is withdraw items (change the item status to "w")
and then suppress the bib record (change bcode3 to "n") in the "Quick Edit"
function of MilCat, but after several records (4-10), Millennium seems to
"freeze."
Here is our procedure:
We scan the barcode of an item, change the status to "w," click "OK," then
click on the "Edit" button, change the bcode3 to "n," then click "OK," then
click the close button, answer "yes" when asked to save changes, then click
the close button to get out of the record completely, then answer "yes" to
save changes.
We then repeat this procedure by scanning in the barcode of the next item.
This seems to work for about 4-10 items/bibs in a row, then when we attempt
to scan the barcode of the next item to work on, the barcode will not scan.
The barcode scanner will beep (sometimes), but no number gets entered in the
box and trying to type in the numbers using the keyboard does not work
either. (yes, the cursor is in the blank box)
We found that if we change to another MilCat function such as "Delete Items"
and then go back to "Quick Edit" we can do another 4-10 items/bibs before it
locks-up again. Likewise, if we close Millennium or reboot the PC, we can do
another 4-10 items/bibs before it locks-up again.
I tried to experiment by only editing the item status and MilCat did not
freeze. However, when I only edited bcode3, MilCat would freeze after 4-10
records, so it seems like editing that field is the cause.
There does not appear to be any problem with the barcodes or barcode reader.
The barcodes are being read just fine using other PCs or barcode readers or
when telnetting or in MilCirc, and the scanners read the barcodes in other
functions like telnet, MilCirc, etc. The freezing also happens when we enter
all the barcode numbers manually as well.
We have reloaded the Millennium Client, but this did not help.
This happens on all three PCs that we use in technical services, so I don't
think it is a PC problem either.
I have opened a call with the help desk, but have not received any response
yet.
Has anyone else experienced anything like this before, or do you have any
suggestions?
Thanks,
Bob

Robert Wing
Librarian
San Jose City College
2100 Moorpark Avenue
San Jose, CA 95128-2799
Phone: 408-298-2181, ext. 3945
Fax: 408-293-4728
E-mail: robert.wing@xxxxxxxxxx