When attempting to remove cleared and/or voided cheques from the outstanding list I have been frequently getting an error message under the title Record Locking "Unable to access record in Check Rec Batch Header. This record is in use by []in window []." I am offered the choice of cancel or retry. Retry returns the same message. Cancel tells me how many records were actually processed from 1 to whatever, but never all selected. Since I am the only one on the system at the time of occurance, I am having trouble believing that someone else has a record, and since the [] is empty, I have no idea where/who the culprit could be. Data Integrity is completely clean. I don't know what to try. Has anyone out there had this difficulty, and if so, were you able to resolve it.

Looking forward to lots of advice.

Thank you.

Sandra

This sounds like an opportunistic locking problem.
Run the Adagio CHKSYS.EXE utility (found in \softrak\system), which checks that the workstation setup has completed correctly, and also identifies if this setting has been disabled. If it hasn't, you will be given the choice to do so.

Hi Sandra,

You might also have a problem with the Semaphore table file (EZSEMTAB.dat) in your data directory. It's purpose is to keep track of which user is doing what, and to warn if one user is preventing another from gaining access.

When nobody is accessing the data, try renaming this file (say the file extension) and it will automatically be created fresh the next time you start Adagio.
--
I've also seen this error before (though not in the function you describe) when a workstation is pretty old with not a lot of memory, and also in the scenario Kate described with certain settings like Opportunistic Locking (or File Caching on Novell Client 32). You might want your I.T. person to give a hand.

It looks like it may have been a problem with opportunistic locking. My workstation is Win98 using the generic MS Client for Netware Networks. We tried on a different workstation running the 3.31 Novell Client(opportunistic locking off by default) and check clearing from the outstanding list completed normally.

I did run the CHKSYS.EXE as suggested and it returned no comments about opportunistic locking possibly because of the older MS Client for Netware.

Renaming EZSEMTAB.dat had no impact on my machine, that is the problem did not go away.

I just wanted to thank you both for your advice.

Glad to hear the problem was resolved.

FYI: the CHKSYS utility will identify the 'Opportunistic Locking' settings found in Windows 2000 or later. It does not (currently) check settings on Client32 (such as Novell) because of the wide variety of choices that differ between Client32 versions. It likely would be too hard to keep up.