Access 2003, Sharepoint Services and muiti ODBC connections

[Guest]

Hello:
I have a two part questions:
1. regarding multi odbc connections within a single mdb: i need to conenct
to tables in different backends. Initially via odbc, using dsn's. Can i
connect to 2 or 3 different backends (SQL or mdb's) from within one mdb? if
not, what is the best approach? (Have one to one mdb to backend connections
and then link an mdb containing the logic to the various connected mdb's /
tables? ).
2. I want to link the logic mdb to Sharepoint so that a broad audience can
view the data: I'm thinking it will be better to convert the odbc connections
to "dsn-less" connections first. My queries will be pulling from backend
tables, accessible from different connections. What are the caveats?

I'm most concerned about ease of use for a select audience--that may not
allow me to "test" any of this from their client.

 

[david epsom dot com dot au]

You can link to multiple MDB's and one SQL Server.

You MAY be able to link to multiple SQL Servers, but you would need to test
that.

You can NOT query against multiple SQL Servers: Access will get lost.
Each Access query can ONLY connect to at most ONE SQL Server (and
possibly only one database in that server - you would need to test
that.)

If you need to connect to multiple SQL Servers, you will not be
able to use Access queries.

Also, you cannot use a DSN to connect to mdb's from within an MDB.


(david)

 

[Guest]

That helps, thanks~

You can link to multiple MDB's and one SQL Server.

You MAY be able to link to multiple SQL Servers, but you would need to test
that.

You can NOT query against multiple SQL Servers: Access will get lost.
Each Access query can ONLY connect to at most ONE SQL Server (and
possibly only one database in that server - you would need to test
that.)

If you need to connect to multiple SQL Servers, you will not be
able to use Access queries.

Also, you cannot use a DSN to connect to mdb's from within an MDB.


(david)