No More Solutions

You can find a lot of debugging and deploying problems while developing applications in .NET and Visual Basic here. There are also some querying tips in SQL and typical source codes which might be useful shared here.

Error detected by database DLL

Error : Error detected by database DLL

This error occurs when trying to open report produced using Crystal Report in application, one of which is application developed using VB.

Solution :
1. If you are using ODBC, make sure the ODBC has been created.

Here are the steps to create ODBC for the connection to the database, press Window + Run, then type "ODBCAD32" (without quotes). Then, on the User DSN tab, press Add.

A dialog box will be shown:



Click the Add button and choose SQL Server.




Insert the name of the database and server.




Next, if you're using SQL Server authentication, insert the login ID and password; otherwise, choose Windows Authentication.





2. If you've created the ODBC in User DSN tab, and still get the error, try doing step 1 again for the System DSN tab while creating the ODBC.

3. If still, it does not work, check the query used in your report, and make sure the stored procedure used in the report (in case you are using stored procedure) has been granted for the application itself. This is sometimes forgotten by developer ^^
To grant the stored procedure to the database user used in the application:
grant exec on spr_spname to database_user_name

Bookmark and Share

5 comments:

  1. batu permata said...
     

    This is sometimes forgotten by developer ^^
    To grant the stored procedure to the database user used in the application:

  2. Steven Luck said...
     

    Yeah... hehehe, it is easily forgotten, especially by developer. In deployment, it should be a more-common issue ^^

  3. Anonymous said...
     

    Thanks man, your solution helped me - I've been struggling with this problem the whole day.
    I forgot to grant permissions on the stored procedure to the db user

  4. Steven Luck said...
     

    You're welcome. Glad to hear it helps :)

  5. Miguel Cajas said...
     

    TenĂ­a el mismo problema pero solo resulto que era el idioma que esta configurado el odbc.

    Mil gracias por que sin esto no hubiera dado nunca que era problema en el odbc.

Post a Comment