Getting Crystal To Work

Oh Crystal, when will you be decommissioned?

Sometimes Crystal just doesn't want to play ball. Here's what I recently found:

  1. If the report was using my local ODBC connection for its Database Connection it didn't work on the Server. Of course.

    I was receiving the following error message:
    Crystal Reports Print Engine error text: Error in File e:\psoft\s90dev\crw\eng\usqsf3p.rpt:
    Unable to connect: .rpt:
    Unable to connect: incorrect log on parameters. %6 %7 %8 %9 (65,30)
    Message Set Number: 65
    Message Number: 30
    Message Reason: Crystal Reports Print Engine error text: Error in File e:\psoft\s90dev\crw\eng\usqsf3p.rpt:
    Unable to connect: .rpt:
    Unable to connect: incorrect log on parameters. %6 %7 %8 %9 (65,30)
    This can be simply corrected by using the following steps:

    - Go to 'Database/Set Datasource Location...'
    - Create a new connection.



    - Select both Current Data Source in top pane and new one in bottom, click 'Update'.
    - Verify the database.
    - Save and perhaps even open and close to ...do something.

    ... or just never using a local ODBC connection (duh?).

  2. Which user to use for the connection prior to migrating out of DEV and eventually into PROD?

  3. Subreport links.

    If found I had to use the following ("sameish" for run control id):


Printing SQR A4 instead of Letter

Bit of a vague post...

When printing directly to Printer we had a Process Type of 'Crystal Check'. In parameters we added:

-PAPERA4

... to the end of the parameter list. This is not documented.