Easysoft
ODBC Drivers for Oracle, SQL Server, Firebird, ISAM, InterBase, Sybase, MS Access & more.

Easysoft ODBC-ISAM Driver

What should I do if I get locking errors from either Easysoft Data Access for ISAM or my legacy application?

Article : 00789
Last Reviewed : 19th July 2005
Revision : 1

If you do find that you are getting locking messages when accessing your files when both EDA for ISAM and a native application are accessing the ISAM files the most likely reason is that your Easysoft locking mode in incorrect. Try changing it by using the following script installed on the server:

cd /usr/local/easysoft/isam/lib

./disam_select.sh

You should then see the following:

Disam Locking Mode Selection

** NOTE : All locking modes may not be available on all platforms **

1. Disam 96 (ISLOCKING = 1 C7LOCKING = 0) (cisam pre 4.1)
2. Disam 96 (ISLOCKING = 2 C7LOCKING = 0) (cisam pre 5.0)
3. Disam 96 (ISLOCKING = 2 C7LOCKING = 1) (cisam 5.0 > 7.1) [default]
4. Disam 96 (ISLOCKING = 2 C7LOCKING = 2) (cisam 7.2)
5. Disam 96 (ISLOCKING = 2 C7LOCKING = 2) (cisam 7.26)

Select required locking mode? (1-5) [3]:

If you do not know the version of C-ISAM that you are running cycle through all versions and one of them will set the locking mode correctly as the Easysoft software has been coded to support all locking modes for all versions of C-ISAM.

Applies To

Knowledge Base Feedback

* Did this content help you?
Yes
No
Maybe
 
* Please select one option based on your first choice:
I'm very satisfied
I think it will help, but I haven't tried it yet
It is helpful, but I need more information
It is helpful, but hard to understand
Seemed relevant in search results, but didn't help me
The information is incorrect
The page contains one or more broken links
 
  Suggest new content or let us know how we can improve this content:

 
  (* Required Fields)   



© 1993 - 2012 Easysoft Limited. All rights reserved.