Skip to Content
avatar image
Former Member

Browse Data & Parameter flds no longer fully populated after upgd SQL 2005

I upgrade our SQL 2000 Server last weekend to SQL 2005 (sp2).

Now our Crystal reports that access SQL data are not working correctly. Parameter Fields are showing little to no data, where before the upgrade we were seeing many more rows in the list.

Digging further, I looked at the fields used for the dynamic LOV. If I use Browse Data on those fields I am seeing the same lack of data. One "Browse Data" that would typically return 80 items now returns 3 items. In that report the data field is DateTime. In another report, the field is string.

I am also seeing an extra check for User Name and password before getting to the Enter values screen for the parameter.

I am using Crystal Developer 11.0.0.1994. It is happening on multiple PCs. I tried with both the original SQL ODBC Driver and the newer SQL Native Client ODBC driver, with the same result.

I've looked at this for 3 days with no luck. Any ideas?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 20, 2008 at 02:44 PM

    have the field types altered (either in type or length) in SQL Server?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Well, I'm giving up on "Why" this happened. I have a solution, of sorts.

      I had some previous minor revisions of this report (2.1) versus the latest 2.8 version. No changes to the datasource or formulas or parameters between the two, just text and formatting changes. Yet this older revision works. So I made a copy and brought the text/formatting up to the current level.

      I still have the constant prompting for a password i.e.

      - "Parameter Prompt" asks for Server Name, Database Name, User Name, and Password on

      each refresh selecting "Prompt for new parameter values".

  • avatar image
    Former Member
    Oct 20, 2008 at 12:50 PM

    have you tried using the newer OLE DB (ADO) Provider as opposed to ODBC ?

    regards,

    dom

    Add comment
    10|10000 characters needed characters exceeded