Crystal Reports 8.5 to 9.0 Conversion 1

[savvy27]

We have the reports for ASP developed in version 8.5 and it was working fine for 5 concurrent users till last week. We upgraded to version 9.0. After doing essential code changes, the version 8.5 reports works good running on web server in which version 9.0 is installed. But when we go to the version 9.0 designer and open the report(which was created in 8.5) It prompts as message for example "The database file "sp_rptSizeandweight;1" has changed. Proceeding to fix up the report" and there is only 'OK' button in the dialog box. When we hit 'ok' it bring up the report after we pass the parameter for the stored procedure. Then when we save or close the report in the designer it prompts that it is a previous version of the report and whether we want to upgrade or not. When we click okay for upgrade(9.0), it saves it and the report is not accessed from the web anymore giving an error message like following:

Active Server Pages error 'ASP 0115'

Unexpected error

/ReportDetail.asp

A trappable error (E06D7363) occurred in an external object. The script cannot continue running.

Please give me your feedback!
Thanks in advance

 

[savvy27]

Hi I'm reposting this message..Please Help.

We have the reports for ASP developed in version 8.5 and it was working fine for 5 concurrent users till last week. We upgraded to version 9.0. After doing essential code changes, the version 8.5 reports works good running on web server in which version 9.0 is installed. But when we go to the version 9.0 designer and open the report(which was created in 8.5) It prompts as message for example "The database file "sp_rptSizeandweight;1" has changed. Proceeding to fix up the report" and there is only 'OK' button in the dialog box. When we hit 'ok' it bring up the report after we pass the parameter for the stored procedure. Then when we save or close the report in the designer it prompts that it is a previous version of the report and whether we want to upgrade or not. When we click okay for upgrade(9.0), it saves it and the report is not accessed from the web anymore giving an error message like following:

Active Server Pages error 'ASP 0115'

Unexpected error

/ReportDetail.asp

A trappable error (E06D7363) occurred in an external object. The script cannot continue running.

Please give me your feedback!
Thanks in advance

 

[JohnEck]

The reports in 9.0 are different in a way that may make them incompatible with the ASP system you have built. Similiar to the reason why CR9.0 reports would not run in CE8.5

 

[itcons4gl]

I was having the exact same problem. Here's what I did to solve it.

1) Make sure you have updated all the asp code to the 9.0 version. Including pages like rptserver.asp, moreRequiredSteps.asp, alwaysRequiredSteps.asp, etc.

2) The logon script to the database has changed from 8.x to 9.0.

I used to use code like:

userid = "dave"
password = "dave3"

Set Database = session("oRpt&quot.Database

Set Tables = Database.tables

Set FirstTable = Tables.Item(1)
FirstTable.SetLogonInfo "DaveProj", "DB", cstr(userid), cstr(password)

Set SecondTable = Tables.Item(2)
SecondTable.SetLogOnInfo "DaveProj", "DB", cstr(userid), cstr(password)

---This code no longer works, you need to do something like this now:

Set mainReportTableCollection = Session("oRpt&quot.Database.Tables


For Each mnTable in mainReportTableCollection
With mnTable.ConnectionProperties
.Item("user ID&quot = "dave"
.Item("Password&quot = "dave3"
.Item("DSN&quot = "DaveProj"
.Item("Database&quot ="DB"
End With
Next

This should work. Unfortunately if in 8.x your Crystal Reports were using Stored Procedures instead of direct queries to the DB tables this code may or may not work. I am still working out the kinks in it. I have found it to work great though with any report that uses direct queries in 9.0.

Hope this helps!

 

[itcons4gl]

Actually something else that I figured out. My previous post isn't really accurate. As long as the asp page (action page) that calls the report is opened in a new window Crystal Reports will no longer throw this error message. In other words on the form action statement say target="new" and it should work.

 

[savvy27]

Thank you all! It works..