ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Crystal Reports, ODBC & Access >> Crystal Reports General Issues >> Formula Error on One Workstation - Crystal 7
http://www.istechforum.com/YaBB.pl?num=1173460282

Message started by Tim Keating on 03/09/07 at 09:11:22

Title: Formula Error on One Workstation - Crystal 7
Post by Tim Keating on 03/09/07 at 09:11:22

I'm hoping Crystal expert Kevin or someone can chime in on this.

I write reports, create executables and point users to the executable on the server.

What would cause one, and only one, workstation to return a formula error when running the report?

The error returned is 'The ) is missing.'

The report runs fine on my machine and the executable runs fine on all machines but one.

I'll post the formula, which doesn't appear to contain this error:

if {BKARINVT.BKAR_INVT_TERMN} = 1 then date(Year(dateadd('m',{@ProxMo},datetime({BKARINVT.BKAR_INVT_DATE}))),month(dateadd('m',{@ProxMo},datetime({BKARINVT.BKAR_INVT_DATE}))),25) else
if {BKARINVT.BKAR_INVT_TERMN} = 5 then date(Year(dateadd('m',{@ProxMo},datetime({BKARINVT.BKAR_INVT_DATE}))),month(dateadd('m',{@ProxMo},datetime({BKARINVT.BKAR_INVT_DATE}))),25) else
({BKARINVT.BKAR_INVT_DATE} + {@DueDays})

Title: Re: Formula Error on One Workstation - Crystal 7
Post by kevind on 03/09/07 at 09:51:29

Would you please post the source for formulas @ProxMo and @DueDays?

Also, the Version of Crystal that you are using.

Make certain that the problem workstation is running the same .exe as the others and not a previous version or interim version you had while developing the report.

Thanks!

Title: Re: Formula Error on One Workstation - Crystal 7
Post by Tim Keating on 03/09/07 at 10:11:42

@ProxMo Formula:

if day({BKARINVT.BKAR_INVT_DATE}) < 25 then 1 else 2

@DueDays Formula:

if {BKARINVT.BKAR_INVT_TERMN} = 1 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 2 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 3 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 4 then 7 else
if {BKARINVT.BKAR_INVT_TERMN} = 5 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 6 then 15 else
if {BKARINVT.BKAR_INVT_TERMN} = 7 then 45 else
if {BKARINVT.BKAR_INVT_TERMN} = 8 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 9 then 31 else
if {BKARINVT.BKAR_INVT_TERMN} = 10 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 11 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 12 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 13 then 5 else
if {BKARINVT.BKAR_INVT_TERMN} = 14 then 10 else
if {BKARINVT.BKAR_INVT_TERMN} = 15 then 30 else
if {BKARINVT.BKAR_INVT_TERMN} = 16 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 17 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 18 then 60 else
if {BKARINVT.BKAR_INVT_TERMN} = 19 then 1 else
if {BKARINVT.BKAR_INVT_TERMN} = 20 then 1 else
30

Everybody points to the same executable from an internal web page that lists our reports.

We're on Crystal Reports 7.01.200

Thanks

Title: Re: Formula Error on One Workstation - Crystal 7
Post by kevind on 03/09/07 at 11:34:40

Another thought came to mind.

If you are using ODBC to access the DBA tables, try the following:
1. Delete the ODBC data source at the workstation thought control panel->administrative tools->Data Sources (ODBC).
2. Close the Data Source Administrator Window (some machines have a bug if you do not close this after Deleting a data source)
3. Go back into control panel->administrative tools->Data Sources (ODBC)
4. Re-Create the ODBC Data Source you need for your report.

See if that makes a difference.

Title: Re: Formula Error on One Workstation - Crystal 7
Post by kevind on 03/09/07 at 12:16:28

Tim,
On a workstation that works correctly, there are several U2*.dll files in c:\windows\system.

Make sure that the workstation that DOES NOT work correctly has these same U2*.dll files in c:\windows\system.

There may be some missing .DLL's used by the Crystal Viewer.

Title: Re: Formula Error on One Workstation - Crystal 7
Post by Tim Keating on 03/09/07 at 12:29:59

kevind wrote:

Tim,
There may be some missing .DLL's used by the Crystal Viewer.

That was it. I copied my DLL's over and the problem went away.

I think it had to do with some non-stock UFL's I thought I had added to everyone's machine.

Thanks a million Kevin.