The information in this article applies to:
SYMPTOMSIn Microsoft Excel, if you return data from Microsoft Query by using the Get External Data command, or the PivotTable Wizard (using an external data source), any column heading that you have renamed in Microsoft Query displays with the original field name, or as EXPR_x (where x is any number) when you return the data to Microsoft Excel. CAUSE
This behavior is by design of Microsoft Excel. When you return data from a
query in Microsoft Query to a worksheet, or to the PivotTable Wizard in
Microsoft Excel, the actual names of the columns in your query are used,
instead of the column headings. This is true whether the field heading is
based on a text value or an expression.
WORKAROUNDTo work around this behavior, use one of the following methods: Modifying SQL StatementNote that you can use this workaround to return data either to a worksheet, or to the PivotTable wizard.Instead of using the Edit Column dialog box to rename a column, you can modify the SQL SELECT statement using the AS clause which allows you to return data to Microsoft Excel with any custom field heading you want. This method creates a non-graphical query, meaning that only the data set is displayed in Microsoft Query. When you run the SQL statement using the AS clause, you receive the following error message in Microsoft Query. Use the following syntax for this type of SELECT statement:
The following example uses the Sales field example discussed earlier.
WorksheetTo work around this behavior when you return data in Microsoft Query to a Microsoft Excel worksheet, do not include the field names when you return the data to the worksheet. Then you can enter your own field names directly on the worksheet. To avoid including field name, clear the Include Field Names check box in the Get External Data dialog box that appears when you return the data to Microsoft Excel.Pivot TableTo rename a field in a Pivot Table, follow these steps:
SQLExecQuery() Function in Visual Basic Module
Microsoft provides programming examples for illustration only, without
warranty either expressed or implied, including, but not limited to, the
implied warranties of merchantability and/or fitness for a particular
purpose. This article assumes that you are familiar with the programming
language being demonstrated and the tools used to create and debug
procedures. Microsoft support professionals can help explain the functionality
of a particular procedure, but they will not modify these examples to
provide added functionality or construct procedures to meet your specific
needs. If you have limited programming experience, you may want to contact
the Microsoft fee-based consulting line at (800) 936-5200. For more
information about the support options available from Microsoft, please see
the following page on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp REFERENCESFor more information about the setup you need to retrieve data with Microsoft Query, click the Search button in Help and type: Query Additional query words: 5.00c 8.00 97 alias wrong
Keywords : kbualink97 xlquery |
Last Reviewed: November 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |