When attempting to use the Lotus NotesSQL driver, you receive messages stating "Function is missing" or "Function not supported", or your application may crash.

You attempt to install NotesSQL, but the install process never appears to complete successfully, so you uninstall it. Now, when you try again to run the install process again, you receive a prompt to repair, modify or remove only. On the select components screen, you see "Space required on ", but you do not see the C drive as an option. You also do not see "Space available on C," or have the option to select the destination folder as you should.

This technote describes how to determine which version of NotesSQL is installed.

It has been found that the NotesSQL 2.06 and 2.05 ODBC drivers are not updating multivalue text fields in Notes correctly.

You attempt to do a query on a Notes database via a .net application, using c# with NotesSQL 3.02e, but it fails with the error: "The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr)."

When attempting to update a document by UNID, NotesSQL causes the server to crash.

You attempt to pull data into an Excel 2000 Spreadsheet from Lotus Notes 6.x, using NotesSQL 3.02e. After selecting the form name, however, you receive the error "Name, constant, or expression expected. Incorrect syntax near SELECT".

You have a Notes database with a hidden design. This database has a form with fields that have input translation or input validation formulas. Using the NotesSQL 2.05 or 2.06 ODBC driver, you attempt to fetch or update data using this form; however, you get an error, and it fails. For example, you are using Microsoft Access 2000 and you want to import data into an Access db using this form. You do a File, Get External Data, Import, and select your DSN, and then select the form from the list of Notes Tables.

When attempting to update existing documents or insert new documents into a Notes database from MS Access 2000, using the NotesSQL ODBC driver, you find that the insert fails. The ODBC trace returns the following error: "DIAG [S1000] [Lotus][ODBC Lotus Notes]SQL Statement is too long (23206)" Modifying the SQL length setting in the NotesSQL Data Source does not resolve the problem.

When a NotesSQL Data Source Name (DSN) has been configured, you can run an SQL query against a Notes database using any ODBC-compliant software. How does NotesSQL present the data from a Notes form or view?