[AccessD] A97 Linked Tables

Hi John

Good question.
It mentions caching, multi-user access, and API calls to the mdb file but what that implies is not clear.

/gustav

>>> jwcolby at colbyconsulting.com 10-02-07 11:50 >>>
What this doesn't discuss is where the performance hit is encountered.  Is
it when a lock is attempted on the BE?  If so then the "hold the be open"
trick would "solve" the issue.  Is it every time a specific table is
referenced in a query?  That would be much more serious since that would
imply no method other than the ones discussed in this KB article would work.

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 Gustav Brock
Sent: Saturday, February 10, 2007 3:10 AM
To: accessd at databaseadvisors.com
Subject: Re: [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