At 10:53 AM 13/04/2005 -0700, you wrote:

>Here's the information you requested.
>
>PING NSTI-2 (from client pc)
>Result: 4 packets sent. 4 packets recd. 0 packets lost.

Good. Confirms that the hostname is solid.

>I am not using Firebird aliasing.
>
>First ADOConnection string:
>Provider=MSDASQL.1;Password=nologin;Persist Security Info=True;User
>ID=nologin;Data Source=AT6Test;Extended
>Properties="DSN=AT6Test;Driver=Firebird/InterBase(r)
>driver;Dbname=\\NSTI-2\C:\Program
>Files\AT6TestData\AUCTIONTRACKER.FDB;CHARSET=NONE;PWD=AEOFAIMBLBAGEBCGHPELFLMPPCGDEIAJIOOENNOPIFGKJCMBHOOLNMKHIMCMAFAIPJMJMJKOLFEIJBAIOGLOABPGPOFOOG;UID=nologin"
>
>Second ADOConnection string:
>Provider=MSDASQL.1;Password=nologin;Persist Security Info=True;User
>ID=nologin;Data Source=CT6Test;Extended
>Properties="DSN=CT6Test;Driver=Firebird/InterBase(r)
>driver;Dbname=\\NSTI-2\C:\Program
>Files\AT6TestData\CONSTITUENT.FDB;CHARSET=NONE;PWD=AEOFAIMBLBAGEBCGHPELFLMPPCGDEIAJIOOENNOPIFGKJCMBHOOLNMKHIMCMAFAIPJMJMJKOLFEIJBAIOGLOABPGPOFOOG;UID=nologin"


>Even though the client machine cannot successfully "Test Connection" in
>the MS ODBC manager (it receives an access error.

This is VERY good, because it demonstrates that the DSN is bad. I'm not an
ODBC user so can't help with this, but there are lots of them. You will
find them and the developer of the Firebird driver in the
firebird-odbc-devel list.

>because the db dir is not shared?)

No. The db dir should not be shared. It will make the database file
unavailable to Superserver. The same applies to the Firebird root directory.

>when I create the data source names AT6Test and CT6Test, I
>make sure the client pc's data source names are defined exactly the same
>as those on the server.

I suspect the "Cannot attach to password database" problem will be found in
the mappings of the Firebird username and password in the provider string
to the security parameters of the DSN definitions. A visit to the right
list is likely to clear this up quickly.

>I am providing all the information I can think of. (One doesn't know
>what they don't know.)

Sure, that's why the people trying to help you ask questions. It gets
really frustrating when these questions go unanswered, or the answer that
comes doesn't respond to the question that was asked.

Whatever, I think that moving this part of your problem to where the ODBC
expertise is will get you close to a solution.

./hb