In order to utilize the user interface capabilities of VB I must be able to access, read, write and update many files within current COBOL Isam files. Some of these files will continue to also be accessed by COBOL applications. I am looking for ideas, or more specifically some form of .ock or .dll that could isolate the handling of the isam routines from the VB programer.