[AccessD] Friday's Puzzler - Table Def "Connection" Info (Database Name)

If you are using identical code to connect to the different SQL databases,
of course with different names, and you have access to different
information, I would have to assume that the privileges and rights are set
differently on each server; OS and SQL.

You should do your testing with ADO-OLE as it eliminates all the extra
potential padding and related errors. I think of ADO like Ping. If it
doesn't work the cable disconnected or the remote PC is down.
 
Jim

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks
Sent: Friday, May 28, 2010 8:54 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Friday's Puzzler - Table Def "Connection" Info (Database
Name)

We have just started to explore the information contained in Access Table
Def  ".connect"



We would specifically like to see the Database Name because we are building
a system that will have a TEST database and a PROD database and we plan to
dynamically switch between the two.



For a test, we linked to one SQL Server table via a User-ID (Windows
Authentication)



We then linked to a second SQL Server table via a SQL Server "Login" (SQL
Server Authentication).  We want to use this approach for the long term.



Here is the part that we don't understand.



When we look at the table def connect info for the first table, we can see
the database name.



When we look at the table def connect info for the second table (SQL Server
Authentication) we CANNOT see the database name.  (This is the piece of data
that we really want to see).



Any ideas on how we can fix this?



Thanks,

Brad
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com