Odbc Driver Lotus Notes Windows 7

I am trying to use IBM ODBC Driver for Notes/Domino 9.0 with Lotus Notes 9 to access distribution lists. I have successfully added a datasource (referencing a server) in ODBC Manager like so: I have added the. IBM Notes location to my PATH, as well as the driver's location.

Understanding the automation test framework of Lotus C API toolkit. Testing products. NotesSQL is the Open Database Connectivity (ODBC) driver for Lotus Notes and Domino databases, and it implements ODBC 2.0 or later specification APIs. Microsoft Windows 2008 Microsoft Windows 7: NotesSQL 8.5.3: Microsoft Windows 2000, XP, Vista, or 7 Microsoft Windows 2003, or 2008 Server Standard Edition or Enterprise Edition: NotesSQL 9.0 (Also called “IBM ODBC Driver for Notes/Domino 9.0”) Microsoft Windows XP or 7 Microsoft Windows 2008 Server Standard Edition or Enterprise Edition.

NotesSQL as suggested elsewhere. However when testing the connection using ODBCTest (or other software), the following error occurs: I suspect this has something to do with not finding the correct notes.ini file (which is mentioned ). I see there are multiple notes.ini files on my filesystem, so I attempted to test each one. I tried appending the location of each of these files to the beginning of PATH in turn, but none of these changes fixed the issue. I also noticed none of the existing notes.ini files are in the.

IBM Notes folder with notes.exe where IBM suggests notes.ini lives by default. Pic basic pro tutorial. How do I: 1) determine which is the correct notes.ini 2) get Notes SQL to recognize that notes.ini, assuming that's the underlying issue. Try running regedit and searching your registry for entries containing 'notes.ini'.

With luck, all the entries that you find will point to the same one. And in general, all programs that use the Notes API should respect the command-line syntax that specifies the notes.ini location using the same equals sign syntax shown above. I'm not sure if that applies to using the ODBC drivers or not, but once you've located the correct path you can try using that syntax in the command line that starts your program. – Aug 4 '16 at 15:33.