Pass through / ODBC Data Source

[Opal]

I am running Access 2003 and was searching
for a solution to my problem and came across
this article:

http://www.techonthenet.com/access/tutorials/passthrough/basics01.php

I have a linked table in my shop database to
my training department's training database.
The problem is, they cannot run their updates
from their database when my "guys" have
their shop database open. I cannot make
any changes to the training database so
I started looking for solutions to make the
linked table, read only. I came across
this tutorial to create a pass through query but
I am puzzled. It should also be noted that
each database is in a separate drive on our
network. Here is my concern, when I go
through the ODBC Data Source Administrator
there is a message that "A User data source
is only visible to you, and can only be used
on the current machine." As my users are on
about 50 - 60 different machines, will this solution work?

Does anyone have any advice?

 

[Jeff Boyce]

Opal

For at least part of your question, ...

ODBC Data Source Names (DSNs) can be user-specific, but they also can be
based on a file.

I have multiple users "sharing" a single DSN. I created it first, then
moved it to a network location, then modified my (pre-distribution)
front-end to use THAT DSN (the one on the network) to connect to the tables.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[Opal]

Sounds like I will have to get my network
support administrator to help with this.

Thanks for the advice.

 

[Jeff Boyce]

Opal

Actually, I did this without my network admin's support (but then, I figured
it would take 10 times as long and involve 10 times as many hoops ... "it's
easier to beg forgiveness than ask permission").

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[Opal]

Jeff,

Unfortunately, I don't have that option.....also, they responded
to my inquery telling me:

"I followed the link you provided and verified that it is not possible
to do an ODBC link to another access database (at least Access 2003)."

Do you have any other suggestions? They had one, but I would
be waiting about 6 months or more for them to implement.... :-(

 

[Jeff Boyce]

I don't understand "link to another access database".

Are you/they saying that the data is NOT in something like SQL-Server, but
is, instead, in an Access "back-end"?

More info, please...


Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[Opal]

I have no idea. My "helpdesk" is less than helpful.

I have created a work around, by building a
go-between database that houses the
linked table, a new table created by
a make table query and then linked
to my shop databases.

This will work until my I.S. Department
gets a clue.... :-S