Currently I'm using ODBC (NotesSQL 8.0 driver/Notes 8.5) to link to various views in a Notes database. In the past it has always worked well, but we recently upgraded to Notes 8.5 and now things are crashing when I try to access one particular view. After extensive research and help from IT support, no solution yet. We have looked at the view itself to see if any issues, such as size, etc., but size is less than others views in same Notes .nsf. Added c:/notes to environmental variables path per NotesSQL help documentation, and tried numerous solutions, including un-installs/re-installs. So far here is what is known:

Other views in same .nsf file are OK. Also sometimes I can access the troublesome view, but not always - it's not consistent and I have to use KillNotes to close Notes completely, re-start Access, refresh the link to the one troublesome view, and then about 50% of the time I will be able to access the data without things crashing. At that point I make a local copy of the data so I can use it as needed with no further trouble. All is well for the day, but each day I need the latest data.

My thoughts now are to try to automate the manual process that is sometimes working. Programmatically kill all running Notes processes and import the one troublesome view. This would eliminate the refresh and make copy part, and not sure why killng Notes works on this view, but so far I have not had success in finding how to import the one view.

I've found Carl Prothman's connection string for Lotus Notes, but getting object required error, and not sure how or if this will help since I'm needing to dig down to the view level and import that.

Not even sure if this will work, but hoping for any ideas.

Thank you, Cathy

Please disregard post. Per IBM support, turns out the NotesSQL driver has a known bug and they're working on it. Plus after Notes 8, the driver versions must match exactly with the Notes version.