>I have this password table we use. The table is read only in all manners but one. There are two fields we use to determine what account number someone is in and a datetime field to determine the time they entered it. The thing is, these records should only be changed by the user who owns that record and logged in as themselves only. Other points of the program will seek those records and read info from them, but do not write anything to them in any way. The problem is occasionally we get locks on certain records anyways. I have the user exit the program and it remains locked by another user until they clear out. I can go into the table, go to the locked record and issue the unlock at the command line and get nowhere. Is there any way to force an unlock on a record? As well, Is there any way to determine in some way who is using (locking) that record?



An approach to consider to prevent such locking is to have the table open as NOUPDATE, then the records should never get into a locked position.

Only when the actual conditions arise that you NEED to allow the update, use the table again (without the noupdate), make the change, then close the "again" version of the table.