At 07:28 20/08/2008, you wrote:

>----- Original Message -----
>From: "Alan McDonald" <alan@...>
>Sent: Friday, August 15, 2008 9:15 PM
>>> Thanks Alan, can I ask a few questions on what you said...
>>> What program would I use to take the backup and create a new copy of
>>> the database with the new owner?
>>
>> gbak
>
>I think I'm making a little progress on this.
>- I created a new user using the IB_SQL tool.
>- I then used gbak to make a backup of the database.
>- I then used gbak to restore the database, but I used the new user I had
>created to do this.
>
>However, when I run my Delphi application and try to access the database, I
>get the following error:
>
>"Project myproject.exe raised exception class EIBInterBaseRoleError with
>message 'no permission for read/select access to TABLE mytable'. Process
>stopped. Use Step or Run to continue."
>
>Even though my new user is the owner, I don't have sufficient rights to
>access the tables. How can I grant these rights to my new user?

You *could* log in as sysdba and grant all of the necessary privileges to that user, including WITH GRANT OPTION if necessary. But it's not ideal. As I and several others have already explained, recreate and pump is the proper solution.

>I'm also interested in knowing what others do when deploying applications
>using Firebird.
>1) Do you send them a link to the Firebird install file to enable them to
>install it or do you include it as part of your install?

Including it as part of the install ensures that they have a Firebird version that's compatible with your application architecture. You also have to cover the situations where Firebird or Interbase is already installed and/or a less than compatible client library and message file are in the client path.

>2) Do you connect to the database using sysdba / masterkey, or do you
>connect using a new owner user you created?

I deploy a security.fdb with the needed user(s) for getting started.

>3) How do you get the end-user to create the Firebird username/password
>required to access the database?

By providing a utility program and the initial sysdba password.

>4) Do you ask the user to enter the username/password each time they run the
>application,

Always. Depending on the security scheme, the username can be defaulted in the login dialog.

>or do you store them somewhere,

That's a possibility, esp. for a demo version

>or do you hardcode them in your application?

Never.

>This is assuming the end-user is not necessarily tech-savvy and your
>application may or may not be on the same computer as your database. In my
>case my application will be available for download as a demo, so anyone
>could be trying it out.

For a demo, in general you don't care about sensitive data so you could store the appropriate login somewhere (ini file or in the client's Registry). Easier still for a demo would be to bypass the authentication route altogether and deploy the demo as a fully pre-built embedded app.

./heLen

>Thanks,
>Stephen
>
>
>------------------------------------
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://www.firebirdsql.org and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Yahoo! Groups Links
>
>
>