When you edit the Data View (also known as Data View Web Part) that contains many list items, performance may be slow. Additionally, performance may decrease as you add more columns to the Data View.

This issue may occur when all the following conditions are true:

• The Data View contains very many list items. For example, the list contains more than 200 items.
• All fields of the Data View are displayed on the Web page.
• Paging is turned off for the Data View.

To work around this issue, turn on paging for the Data View and display only a few items. To do this, follow these steps:

1. Click Style in the Properties list for the Data View.
2. Click the Options tab, click Limit the total number of items displayed to, and then type the number of rows that you want to display per page.
3. Click OK, and then test your page.

Note If paging did not seem to work, and you still return all the items in a single page of the Data View, make sure that the data source that you are using has a primary key and that you include it in your custom query.

Data Views display data by using Extensible Style Sheet Language Transformations (XSLTs). When you use FrontPage to create or edit a data-driven Web site that is located on a server running Windows SharePoint Services, you can add Data Views that extract data from a variety of available data sources, including .xml files, Web services, SharePoint lists, and OLE database–compliant databases such as Microsoft SQL Server, DB2, and Oracle. You can also customize Data Views to create custom views of your data in WYSIWYG format by using the Formatting toolbar or by using the Data View Details task pane. Windows SharePoint Services provides the component-based platform required for FrontPage data-driven functionality.

For more information about working with Data Views in FrontPage 2003, see FrontPage Help. To do so, on the Help menu, click Microsoft Office FrontPage Help. In the Search for box, type data view, and then press ENTER to view the topics returned.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.