Folks:

I have a number of procedures (reports and modifys) that run every day in ReportCaster with no problem.

I've recently created 3 versions of the same report (one for salesmen, one for Customer service Reps and one for Management) that fail every time I schedule them in ReportCaster.

However, they do run without a problem from Dev Studio. And if I simply run just one of the reports in Dev Studio and then switch over to ReportCaster they will run just fine.

The ReportCaster job logs say "Fieldname or computational element not recognised:[+fieldname]"

Now all the fieldnames in question are the result of a join. I'm guessing that the apppath or something like that isn't correct - or at least not correct enough for ReportCaster.

Note that there are no amper variables involved.

I welcome any suggestions...

This message has been edited. Last edited by: George Patton,

If I'm running a task from Reportcaster that is calling a fex with masters from an application folder that is not in the normal application path - I've had to include a path command at the top of the fex such as:

APP PREPENDPATH SALESTAX

Otherwise I would get an error statement similar to the one you got. I reset the paths at the end of the fex also with: APP PATH


Norb

This message has been edited. Last edited by: Norb Eckert,

Use WHENCE command to locate application folder of the master file and make sure that is as expected.
If there are multiple master files in the same name and that folder comes first in APP PATH search list, you will get similar error in Report Caster.

Hope this helps.

Thanks,
-Ram

I used Norb's suggestion and it seemed to work this morning on one of the reports - I've modified the others and we will see if everything runs smoothly tomorrow.