[AccessD] Changing the ODBC Connection String to use UNC - Strange Results

Hi Charlotte

"Safe" is not the word to use. It has worked for us and _all_ our clients
since our first use of Access with a shared backend file on a NetWare server
in 1994 with 0 (zero) issues.
Even today where we have a setup of DFS linked file servers in AD where
physical UNCs are replaced by virtual server names (like:
\\domain.local\company\data\database) we still use drive mappings controlled
by a logon script. Thus, no matter which machine - even a brand new just
attached to our domain - I login from and which server I physically get
connected to, I always have the same drive mappings. So: Different machines
do have identical mappings". And servers can be replaced, added, or removed
invisible to the users.

All that is required is an orderly environment.

/gustav


-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af Charlotte Foust
Sendt: 23. oktober 2012 01:58
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] Changing the ODBC Connection String to use UNC - Strange
Results

It's not safe to rely on drive mappings.  Different machines may have
different mappings.  I always convert to UNC on LANs.

Charlotte

On Mon, Oct 22, 2012 at 3:10 PM, Stuart McLachlan
<stuart at lexacorp.com.pg>wrote:

> Same here.  Always use UNC for linked Access tables.
> For ODBC, it depends on the BE, sometimes UNC, sometimes IP address - 
> but I never rely on drive mappings.
>
> --
> Stuart
>
> On 22 Oct 2012 at 13:56, Heenan, Lambert wrote:
>
> > I *never* use anything *but* UNC paths for linking table - admittedly
these are direct links via the Access UI, not ODBC links.
> >
> > Lambert