ngong
ngong

Reputation: 882

ODBC access to Sparx Enterprise Architect Firebird file

Using the newest Enterprise Architect (EA16) gives the ability to store models in a Firebird database file with extension feap.

Installing EA16 on Win10 also installs an ODBC driver, named EA Firebird ODBC driver.

If I try to install an .feap-file to Win10 ODBC sources for that driver, I am asked for a User, Password and Role specification that I was not able to find out. I have tried no specification, SYSDBA/masterkey and ADMIN/password - without success. I have asked at Sparx Forum - without success.

Do you know these credentials? Or: is it possible to enter a new user/pwd to an existing Firebird DB file, granting priviledges?

Upvotes: 0

Views: 405

Answers (1)

Mark Rotteveel
Mark Rotteveel

Reputation: 109090

The following answer is based on a number of assumptions. I don't know Enterprise Architect, so I cannot experiment to verify this.

I think Enterprise Architect uses the Firebird Embedded library, and doesn't actually have a Firebird server running. Based on the first bytes mentioned by qwerty_so in the comments, it seems it is using Firebird 2.5 or earlier.

Based on this information, you can do the following:

  1. Find out where Enterprise Architect has the Firebird Embedded library (fbembed.dll by default), and reference that as the client library in your ODBC config (this only works if that library matches the bitness of the application where you want to use the ODBC data source)
  2. Download the Firebird 2.5 embedded library of the right bitness from the Firebird 2.5 download page (i.e. Firebird-2.5.9.27139-0_Win32_embed.zip or Firebird-2.5.9.27139-0_x64_embed.zip). Configure your ODBC data source to use that as the client library

Firebird Embedded requires a username, but doesn't perform authentication, so the password is ignored, and any user name should do (though you should use one with sufficient permissions, so likely SYSDBA is the best choice).

  1. Install a Firebird 2.5 server, and connect through this server to the database file.

    With this option, you're in charge of the credentials, so use the SYSDBA password you configured in the installer.

Upvotes: 2

Related Questions