Openning a Crystal Report in Design mode from code.

[a2ross]

I have a report that is populate from a VB data object and called from a VB Crystal Reports object. Since upgrading to Crystal 8.5 some of the data fields are not being picked up by the report.

I am trying to debug this but cannot access data by openning the report manually as it won't pick up the runtime data source.

Can this be done? Alternatively, how do I create a new report to access the data from a runtime data object?

Please help as this is urgent.

 

[balves]

This is one of the worst features of Crystal. Once you've created a report off of an ADO recordset, it's very difficult to see how to change things later.

If your ADO SQL in VB no longer matches the fields in the report (i.e., the SQL statement that originally created the report), you have a problem.

You can get back to the ADO SQL query in the report design and fix it. Use the menu choice "Set Location" to go back through the dialog boxes, choosing your data source, then clicking the "Set" button and "Done" and hopefully your SQL will appear in a non-sizable window. You can fix the SQL there to match the SQL in VB, hit OK, and then you'll get a message saying "ADO has changed - fix up report?" and one more affirmative click and you're all set.

It would be much easier if there was just a direct menu choice for editing the SQL of the ADO recordset. If there is, I haven't found it. Brian J. Alves
Terrier Consulting, Inc.
Email: brian.alves@worldnet.att.net
VB / Crystal / SQLServer
(Currently available for consulting in Chicago)