ACC: How to Change the Order of Columns in a Chart (95/97)

Last reviewed: May 5, 1997
Article ID: Q141235
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

SUMMARY

Advanced: Requires expert coding, interoperability, and multiuser skills.

By default, a chart sorts the X-axis fields in alphabetical or numeric order. This article describes two methods you can use to sort the X-axis fields in a different order.

MORE INFORMATION

There are two methods you can use to change the ordering of fields in a chart. The first way is to add an Order By clause to the SQL statement in the chart's RowSource property. The second way is to create a query that orders the fields the way you want them, and then to use the query for the chart's RowSource property.

How to Create a Sample Chart

To create a chart, follow these steps:

  1. Open the sample database Northwind.mdb.

  2. Create a new, blank form not based on any table or query.

  3. On the Insert menu, click Chart, and then click in the Detail section of the form where you want the chart to appear.

  4. In the Chart Wizard dialog box, select the Sales By Category query as the data source for the chart, and then click Next.

  5. Add the CategoryName and ProductSales fields to the Fields For Chart box, and then click Finish.

  6. View the form in Form view. Note that the CategoryName records are listed in alphabetical order.

How to Change the Chart's Sorting Order

Method 1

The following example demonstrates how to add an Order By clause to the SQL statement in a Chart's RowSource property:

  1. Open the form that you created in the "How to Create a Sample Chart" section in Design view.

  2. Select the chart.

  3. On the View menu, click Properties.

  4. Select the RowSource property of the chart, and then press SHIFT+F2 to zoom in on the window. Note that the RowSource property's Select statement reads as follows:

          SELECT [CategoryName],Sum([ProductSales]) AS [SumOfProductSales] FROM
          [Sales by Category] GROUP BY [CategoryName];
    

  5. Type "Order By SUM([ProductSales]) desc" (without the quotation marks) before the semicolon at the end of the SQL statement so that the SQL statement reads as follows:

          SELECT [CategoryName],Sum([ProductSales]) AS SumOfProductSales] FROM
          [Sales by Category] GROUP BY [CategoryName] Order By
          SUM([ProductSales]) desc;
    

  6. Click OK.

  7. View the form in Form view. Note that the CategoryName records are now listed in descending order of sales.

Method 2

The following example describes how to create and use a query for the chart's RowSource property:

  1. Re-create the form with a chart that you created in the "How to Create a Sample Chart" section.

  2. Select the Chart.

  3. On the View menu, click Properties.

  4. Using the right mouse button, click the RowSource property, and then click Build.

  5. In the SQL Statement: Query Builder window, set the sort order for the ProductSales field to Descending.

  6. Close the SQL Statement: Query Builder window and save the changes.

  7. View the form in Form view. Note that the CategoryName records are listed in descending order of sales.

REFERENCES

For more information about ordering fields, search for "order by clause" using the Microsoft Access 97 Help Index.

For more information about this topic in earlier versions of Microsoft Access, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q109315
   TITLE     : ACC: How to Change the Order of Columns in a Graph (1.x,
               2.0)
 

	
	


Keywords : IntpGrph kbtool
Version : 7.0 97
Platform : WINDOWS
Hardware : x86
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.