After toying with this all day, it would appear my problems are many. Creating a gds32.dll (usning instclient.exe) certainly helped with the connection problems. But when I looked at my data (logged in as sysdba) I had garbage characters in a number of fields, one of them a memo field.

Tell me, is it possible to use a security2.fdb that resides on my development PC, when talking to a DB that resides on a different server PC? EMS SQL Manager gives me an option to tell it where the security db lives. But it seems like a HUGE problem if I can use the seucirty DB on a different PC to access a DB on another PC.


I've been tinkering with FB since 1.5 (I am running on Win2K btw) and now at 2.0.3. Between 1.5 and 2.0 I did a backup/restore to update the ODS. Do I need to run such a procedure between all revs? ie 2.0 to 2.0.1? I wouldn't have thought so.

finally, I am running the latest rev of EMS SQL Manager 2005 - version 4.4.0.5. It claims to support both IB and FB. Is it possible that changes have been made in the FB internals making it no-longer compatible?

I am now more concerned about the data corruption then my privilege issue. so tomorrow I'll give it a fresh start (all dummy data at this time) and see what happens. But my first impression is that FB is perhaps not so stable. After all, I didn't exactly hit FB over the head with a sledge hammer. I was trying to follow best practice (ie the backup/restore business) and I still managed to mangle the data.

I am too new at FB to really know where to point the finger. I know all the "gotchas" for Paradox tables. I would imagine this will be Lesson #1 when I sort it out.

ta
-randall

ps- have you updated your book to fully cover 2.0? The version I have covers up to 1.5 and talks about 2.0 but clearly was not released when my copy went to press. bloody great book! best and only reference book needed, once it covers 2.0 in full.


Helen Borrie <helebor@...> wrote: At 03:22 AM 7/11/2007, you wrote:

>I have a question about creating other DB users (using FB SuperServer 2.0.3)
>
>I've created a very basic DB, it has only 2 table, no views or triggers, etc. I can work with the DB fine as sysdba. I then went and created a user "x" with pw "x" and tried to login (Using EMS SQL MNager 2005). The "test connection" button says it is OK, but when I try and actually login I get an error. something about "DB shutdown" or "Operation Aborted"

Those are not Firebird errors. Either the client you are using has some kind of interpretation layer for exceptions or you are misreporting the error text. If you get a 9-digit error code with an error message then it should be a Firebird error.

Also, if the client has "2005" in its title it's quite possibly well out of date for use with Fb 2.0.3. Try using isql or an updated version of the client.

>but I don't understand what other permissisions I need to grant. I've done a "grant all" for my 2 tables.

What you *seem* to be experiencing is a problem with access to the server rather than privileges for the database objects. If the client program is really interpreting the exception as "DB Shutdown" that seems to mean the client couldn't get the server to respond. It might mean the server wasn't actually running...."Operation aborted" might be anything, possibly some generic message the application delivers when it can't work out what's going on.

>what am I missing?

Is there anything in firebird.log?

You haven't said what platform the server is [meant to be] running on. With SS that matters: you can't use a connection string without the hostname if your SS is on a POSIX platform.

If it's on Win2003 or Vista a non-network connection path won't work either, since your client would be running in a remote desktop shell.

Have you looked at the Quick Start Guide in the /doc/ directory?

./heLen




__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Non-text portions of this message have been removed]