[AccessD] A97 Linked Tables

Hi Lambert

Thanks for pointing this out. I've never heard of the problem with long filenames but it certainly may explain some experiences we have had through the years.

/gustav

>>> Lambert.Heenan at AIG.com 09-02-07 23:19 >>>
Never heard of any problem with using UNC paths. You may be confusing that
with using long filenames in paths.

If you are linking to a file in "\\server\share\Some Long Path Name\And a
SubFolder" then you can get a performance hit as the OS has to walk the
folder path resolving long file names to 8.2 file names.

To eliminate that problem you can use the short file names in the linked
file path, like

\\server\share\SomeLon~1\AndASu~1

See http://support.microsoft.com/kb/891176/en-us

Lambert


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Friday, February 09, 2007 4:29 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] A97 Linked Tables


I could swear though that unc mapping was slower than physical mapping. That
may have been fixed long ago however.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Friday, February 09, 2007 3:10 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] A97 Linked Tables

No "mapping" is required.

In Access when you browse to where the back end is to link to its tables,
instead of selecting the drive letter and browsing to the folder with the
MDB file, type 
	\\SERVERNAME\SharedFolderName
in the file name box of the file select dialog box. Hit enter and then you
will see the folders on the share and you can browse to the backend. The
paths stored within the front end will then be UNC paths instead of mapped
drive letter paths.

HTH

Lambert