Hello, all.

When a user invokes a ctl-spacebar lookup does this place a table lock?
Yes, I know it does.

simply put

Student --->> Purchase --->> Bookitems(which looks up from books.db)

On my system, when one operator is searching for a record on the lookup,
then a user on another machine is unable to calculate a total of their
Bookitems.

We solve this effectively if crudely by yelling across the room "will
someone hurry up their lookup so I can get my total".

Surely this can't happen on large systems with dozens of people using a
lookup, the system would be unworkable?

Is there any way around this? I thought about a button to play a tune to
the offending lookerup, but something more elegant is needed I feel.

I do have an automatic retry loop and a notice telling the operator what
is happening and what to do.

Regards
Anne

-----
Anne Wainwright
Please reply to group

you should be doing that calc by scanning the restricted records that apply,
not by using the "calc" functions.. because of the locks the "calc"
functions place..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Anne Wainwright" <duffaddress (AT) ananzi (DOT) co.za.invalid> wrote

"Anne Wainwright" <duffaddress (AT) ananzi (DOT) co.za.invalid> wrote

Steve gave you one solution by fixing the CALC, which is the more
elegant way.

The other way is to simply make a COPY of the BOOKS.DB, call it
BOOKSTOO.DB, and base your lookups on the copy, not the original.
If any one edits the original, add a line to copy the table to the copy.
This
introduces the possibility of mismatch between the two copies (sync
problem), but unless you have very frequent edits of the BOOKS.DB
this will likely NOT be an issue. You could simply require a FULL LOCK
on BOOKS.DB editing to prevent anybody else from entering an order
while someone updates the BOOKS.DB, which would sorta makes sense.
And only release the full lock when BOOKSTOO.DB is updated as well.

--KC

Hi,

Thank you both, Steven & Casey.

I'll look at Stevens method as in fact there are ongoing edits all day of
price and yes/nos as the stock changes. I could see clashes.

Regards
Anne


"Steven Green" <greens (AT) diamondsg (DOT) com> wrote in
news:45d36b6d$1 (AT) pnews (DOT) thedbcommunity.com:

--
-----
Anne Wainwright
Please reply to group