Re: [Firebird-odbc-devel] ODBC connection fails

[Helen B. <he...@ii...>]

At 10:37 AM 16/12/2010, Ken Benson wrote:
>>>>Whoever wrote those apps has hard-coded a username and password into
>their code, that are not the SYSDBA/masterke combination 
>>>>that the whole world knows (which is *entirely* expected).  If you know
>what they are, then you will have to set them up in 
>>>>your server.  There's no way to discover them if you don't know them.
>
>
>Just so I'm clear - you mean the two apps I'm trying to connect using ODBC,
>right?

I guess so.


>Here's the deal - one of those apps is MAP DESIGNER from Pervasive. It has
>fields for User/password - and if the ODBC connection is left blank, this
>application prompts with a box for USER/PASSWORD/ROLE ... nothing I put in
>this box satisfies the app.

Then that says the access to the objects you are trying to access have been (correctly) set up with SQL Privileges that have been bundled in a ROLE.  SQL Privileges belong to a database, not a server. 

This is *still* not an ODBC issue...If you have been connecting to that database using isql (which doesn't use ODBC) and the SYSDBA credentials *for your server*, you should be able to ascertain the roles that have been defined in that database, using SHOW ROLES.  SHOW GRANT should show you the name[s] of the user[s] that have been granted the respective roles.  To make it work, you will need to define that/those user[s] in your server's security database, logged in as SYSDBA.  And then, when you attempt to connect, you will need that user's login credentials PLUS the role name (which may or may not be case-sensitive, so assume it is...copy exact case from what SHOW ROLES displays and wrap in double quotes if SHOW ROLES displays something other than all-caps.

>The other app is the Database Browser. It has the capability to connect
>directly - or via ODBC. It will connect to the database, directly. It will
>NOT connect to the same database via ODBC.

If we are talking about the same database browser (DBrowser.exe) then look at my posting from last week, which shows a screenshot of a successful ODBC connection made by that application.  However, that browser is pretty generic...it probably doesn't even know about roles.

HB