Edit

Share via

Error message when you print a report in Microsoft Dynamics GP: "Undefined Symbol"

  • Article

This article provides a solution to an error that occurs when you print a report in Microsoft Dynamics GP.

Applies to:   Microsoft Dynamics GP
Original KB number:   862263

Symptoms

When you print a report in Microsoft Dynamics GP or in Microsoft Business Solutions - Great Plains 8.0, the following error message is printed on the report:

Undefined Symbol

Cause

This problem can have any of the following causes:

Cause 1

This problem occurs if the following conditions are true:

  • You put a field in a footer or in the report body.
  • You change the field type to a type other than data.
  • You use the report field in a calculated field, and then you remove the report field.
  • You do not change the calculated field.

See Resolution 1 in the Resolution section.

Cause 2

This problem occurs if the following conditions are true:

  • You set up a calculated field that uses another calculated field in an expression.
  • You delete the first calculated field.

See Resolution 2 in the Resolution section.

Cause 3

This problem occurs if the following conditions are true:

  • You set up a sorting method that has one or more fields.
  • You create additional headers or footers that use these fields to break on.
  • You remove these fields from the sorting method.

See Resolution 3 in the Resolution section.

Cause 4

This problem occurs if the following conditions are true:

  • You have a restriction, a sort, or a field on a report.
  • The file from which the restriction, the sort, or the field came has been removed.

See Resolution 4 in the Resolution section.

Cause 5

This problem occurs if you have an invalid relationship that is defined between tables. See Resolution 5 in the Resolution section.

Resolution

Use the corresponding resolution according to the cause.

Resolution 1

To resolve this problem, change the calculated field after you remove the report field.

Resolution 2

To resolve this problem, do not delete the first calculated field.

Resolution 3

To resolve this problem, do not remove these fields from the sorting method.

Resolution 4

To resolve this problem, remove any restrictions, any sorts, or any fields that came from a file that has been removed.

Resolution 5

To resolve this problem, determine whether there is an invalid relationship between tables. To do this, follow these steps:

  1. Create a new report.
  2. Add one table relationship pair to the report, add fields from the linked tables, and then perform a test print of the new report.
  3. Repeat step 2 until you receive the error message that is mentioned in the Symptoms section.
  4. When you receive the error message, review and then correct the last relationship definition that you added.

Disclaimer

Microsoft and/or its suppliers make no representations or warranties about the suitability, reliability or accuracy of the information contained in the documents and related graphics published on this website (the "materials") for any purpose. The materials may include technical inaccuracies or typographical errors and may be revised at any time without notice.

To the maximum extent permitted by applicable law, Microsoft and/or its suppliers disclaim and exclude all representations, warranties, and conditions whether express, implied or statutory, including but not limited to representations, warranties, or conditions of title, non infringement, satisfactory condition or quality, merchantability and fitness for a particular purpose, with respect to the materials.