Microsoft How-To: Removing a Subdatasheet

Subdatasheets are a neat feature added to Access in the 2000 version, but for anyone building applications, especially when deploying over a network, they should probably be turned off. You'll use your own forms instead of this "free" database feature, and they can cost you in terms of performance.
This article shows how to remove them in Access 2007. In 2003 the remove option is under Format/Subdatasheet.

Also see this great UtterAccess post by Crystal at UtterAccess.com on Subdatasheets, which includes links to articles that discuss the performance issue.

**Links cleaned up 2011-09-05**

Help Access run faster

The Microsoft Office Online team has posted a new rundown on performance considerations for Access here. Some of the tips are also in other articles I've linked previously, but this looks like a good list.

Best Practices When Using Microsoft Office Access 2003 in a Multi-user Environment

This Microsoft article runs through a raft of things you should think about when deploying Access in a multi-user environment. It's not comprehensive, so review my other posts on multi-user deployment as well.

Deploying an Access Application over a Local Area Network (LAN)

This page runs through a variety of topics related to deployment in a LAN environment, including (among others)performance suggestions and splitting your database.

It includes links to a variety of tips and references, as well as some specific techniques.

Note that the suggestions to use a batch file to deploy front-ends may not be "best practice", there are other alternatives to accomplish the same goal. You should review these and determine which fits your situation best.

deployment, multi-user, performance,network

Microsoft Access Performance FAQ- Tony's Microsoft Access Page

This page is a collection of performance related topics from Tony Toews, a Microsoft Access MVP.

How to optimize Office Access and Jet database engine network performance with Windows 2000-based and Windows XP-based clients

From the Microsoft Knowledgebase.

When you run a Microsoft Jet database engine-based program, such as Microsoft Office Access, on your Microsoft Windows 2000-based or Microsoft Windows XP-based computer, the program may appear slower and less responsive than you expect. This article contains information about how you can optimize network performance for Windows 2000-based and Windows XP-based computers. Doing this can make Office Access and Jet database engine-based programs more responsive.

   #