Kenny,
I will give you my standard answer and a suggestion:
This is probably a power, nic, or network problem. I would check them in that
order.
My suggestion is: Don't delete rows when the system is busy. I update the
key columns changing them to -1 and then I delete them when I am in single
user mode just before I do a reload. This cuts down on a lot of overhead.
Troy Sosamon
>===== Original Message From [EMAIL PROTECTED] =====
>Using RTime65++ for DOS multiple users using a single table edit form (to
>update a single column with expedite information). We are receiving the
>following sequence of messages several times daily. "Internal Lock Error"
>"Have all users disconnect from the database" "unavailable resource
>encountered during RETURN command (2440)"
>
>This is a Purchase Order application and other users may be inserting new
>rows, or using a two-table form to edit other purchase orders or deleting
>rows, or receiving my be updating these rows.
>
>The users have started ignoring the warnings and are able to return to the
>form and make the edits without further problems.
>
>The database autochks OK and I have not discovered any consequences to the
>users continuing on.
>
>Questions:
>
>1. What exactly causes this? Two users on same row, same column?
>
>2. Is there any real problems here or does RBase resolve the lock problem
>on its own?
>
>3. Should I demand (again) that they follow the message and get all 35
>users out of the DB? (They hate this.)
>
>4. Is there some way to work around this?
>
>Kenny Camp
>IT Manager
>Electro Enterprises, Inc.
>405-427-6591
Troy Sosamon
Denver Co
[EMAIL PROTECTED]
