What to check

A report moved from test to production may encounter different user-defined fields or database metadata. A command using SELECT * can make that difference more significant by bringing unused fields into the report definition.

Troubleshooting steps

  • Compare the report's expected fields with the target company's supported schema, including referenced user-defined fields.
  • Replace unnecessary wildcard selection with the explicit columns the report actually needs and review dependent formulas.
  • Use Crystal Reports database verification on a report copy connected to the correct target environment, then test representative records.

Confirm the result

Confirm that each section renders and totals match. Do not alter the production company's schema merely to make it resemble an unrelated development database.

References

Official documentation (English)