8.3 File Name Convention - Short File Names

[sgrace]

Hello all.

We run multi-user Access 2010, split, on the root of a Windows 2003 share drive with a mix of XP and Win7 clients.

Seeking opinions. There's an older MS article (889588) that recommends 8.3 file naming convention for faster performance. Given that Access now has 4-letter extensions (Ex: accdb), you have to step outside the bounds a bit to use 8.3.

Just curious if anyone has tried 8.3 and experienced any response time difference.

Any other recommendations related to that article, or otherwise? For instance, does turning off the sharing violation notification delay have an appreciable effect?

Thanks in advance.

 

[boblarson]

Small world. I posted an answer for you here:
http://answers.microsoft.com/en-us/...le-names/a06dda35-e117-4e9e-8b09-01c69e353acbhttp://access-freak.com/tutorials.html#Tutorial05

 

[sgrace]

Thank you Bob. Twice. : )

 

[gemma-the-husky]

i think the sharing violation fix might be worth trying - but the best solution to timing issues in multi user databases must be to maintain a persistent connection

you can see it when you link tables in a database that is in use - say 20 tables

if you just link the tables normally in code, it will probably take a good few seconds to link all the tables. If you open one, and then set a persistent connection to it beforeo pening the others, the link time drops to maybe 2 or 3 seconds.

 

[sgrace]

Dave,

Yes, I've seen you reference the file sharing violation notification delay in other posts. Will give it a try.

By the way, I do have persistent connection mechanism in place. Definitely a good thing.

Thanks.