X-no-Archive:yes
Query issues a conditional lock all the time, when it reads and when it
writes. If some program has a conflicting lock, Query comes back to you
with the prompt you describe.  If you answer yes, Query then uses an
unconditional lock and will not prompt again for the duration of the
current command.

You can instruct Query to not lock during reads by issuing the command SET
LOCKOPTION=OFF.  This leads to better overall performance, but be aware
that you may encounter ephemeral broken chains.  This would be were you are
reading down long chains and some other program changes an entry on the
specific chain you are reading.  Since Query is not locking anymore,
something might move out from under it.  It is rare but it can happen.

Kind regards,

Denys. . .

Denys Beauchemin
HICOMP America, Inc.
(800) 323-8863  (281) 288-7438         Fax: (281) 355-6879
denys at hicomp.com                             www.hicomp.com


-----Original Message-----
From:   Costas Anastassiades [SMTP:[log in to unmask]]
Sent:   Wednesday, 24 June, 1998 6:07 AM
To:     [log in to unmask]
Subject:        DATA BASE BUSY

When and why does the "DATA BASE IS BUSY DO YOU WANT TO WAIT" message come
up in Query ? Any way to turn it off or default it to yes ?
I was trying to execute a long XEQ file only to come back and find that
this
prompt came up and was "consuming" subsequent commands as answers.

Many thanks as always.

p.s. On a side note concerning the recent batch of email messages showing
up
as attachments, I found that all is well if the message is sent as Plain
Text and UUENCODE (not MIME). The second being the important option. I'm
sure you loose some of the bells and whistles of fancy email messages, but
in my opinion messages of that nature are better sent as attachments
anyway.

Costas Anastassiades,
Intracom SA
Athens-Greece