The remaining text does not appear to be part of the formula

[jennone]

This message is received when I run a Crystal report developed in version 8.5 from a VB client app installed on a Windows 2000 server.

The same report, run from the same client installed on an NT box does not generate this message. It gives the appropriate information.

Both PC's are hitting the same database. (SQL 2000)

The report SQL is "SELECT
admin_history2."users_full_name", admin_history2."table_name", admin_history2."alternate_index", admin_history2."alternate_index2", admin_history2."time_logged", admin_history2."status"
FROM
"mis"."dbo"."admin_history2" admin_history2"

The Crystal runtime .dlls are the same on both boxes.

Any ideas?

 

[BruceBussell]

jennone,

Windows 2000 can get kind of contrary when trying to print reports from a front end program if the ODBC DSN you are using is a USER DSN and not a SYSTEM DSN.

Windows 2000 often will not let another user run a report if it was created on a computer that used a USER DSN to create the report. Note that the Report Set Location section records much of the ODBC DSN info in the report itself.

Have you checked to see if you are using a SYSTEM DSN ODBC connection on both machines, as well as the one the report was created on.

Bruce

 

[dgillz]

Please show the record selection formula rather than the SQL.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[jennone]

We are using System DSN's on all client PC's and the Windows 2000 server. The report creator thinks he probably used a System DSN when he created the report, but does not remember if this report was created in v 8.5. I did check it out of version manager, check the ODBC connections, verify the database connections and save it on my PC. (No change in the error message)


The report does not have a record selection formula. The VB app is handling the selection. The report uses parameter fields. We are using some formula fields with selection criteria, again, values are passed in from the VB app.

 

[kscheeler]

It could be an issue with the c:\windows\crystal folder not being present on one of the computers or not all of the files in there. You're getting that error from one of the formula's. It doesn't recognize one of the functions that's being used like NumberToDate() or something.

From the computer that it doesn't work from, open the report in crystal and hardcode the prompted values and see if the report runs. If not, review which formula and which function is it crashing on.

Kevin Scheeler