Linked Table - How to reference them

[WayneRyan]

Hi all,

This issue revolves around the way that users
see and reference my Access server.

Users live in Domain A and the server lives
in Domain B. When the launcher for the application
starts Access it constructs the command line
as follows:

strAccessPath = """C:\Program Files\Microsoft Office\Office\MSACCESS.exe """
strDBPath = "\\20.2.100.11\efs$\efs2k.mdb "
strWorkGroup = "/wrkgrp ""\\20.2.100.11\efs$\system.mdw"" "
strOther = "/Nostartup"

The IP address is "NATed" and this works well and most
users have no idea where the actual application and
data reside.

The users can't even see the server when they use
the Explorer.

The problem is that since the main application has
references to MS Project, Excel, etc. and all users
don't have these. Their timecard entry screen is
now a stand-alone (very small app) that doesn't require
these references. So far, so good. This new app must
LINK to the main app's tables.

1) Establish links on the server. No, "C:\efs..."
is not how the users see the server.

2) Map a network drive and from that set the links.
No, then all users have a mapped drive containing
our software and data.

3) Find a way to link using the NATed IP. No the
Link Manager can't see it in this context.

Solution: Edit MySysObjects and change the database
path to the NATed ip address. The s/w will see it
and the users can't "browse" it.

Any ideas?

Thanks,
Wayne

 

[WayneRyan]

Additional info:

How about programmatically setting links.
Can it be done?

Thanks,
Wayne

 

[allanon]

What about thru ODBC and then lock down the odbc administrator? It is easy to change odbc links in an app.

 

[WayneRyan]

allanon,

Thanks for responding. I did find a code fragment that
let me programmatically set the ".connect". Naturally
this led to the well-documented "Can't find installable
ISAM" error message. This is either a missing driver
or an invalid registry reference.

I think this topic is covered.

Thanks again,
Wayne