Our developer had a spelling error with the name of a report when he initially created a fex file for us.

we fixed the spelling error in the report itself, but the actual fex file name still has the report name wrong, and this is what shows up in the schedule information.

We tried to rename the fex file on the server, but it didn't work. It still kept the old file name.

If we name a fex file wrong to begin with, is there anyway to fix this?

This message has been edited. Last edited by: LoriBlake,

I'm a begginner, so there may be a better way, but our dba said that to get the names to match, in developer studio, right click on the file and choose Edit In Text Editor. Select All (ctrl+A) Copy, Close the file, In developer studio, right click and choose New Procedure, Give it the name you want, Create, go to text view and paste, Save it.

File should now have same name for Name and File Name.

HA HA HA! Good answer!

What sxschech described is exactly what we all (or most of the ones I know ) must do when we don't like or simply misspelled the procedure name in the MRE.

The problem with this approach is that it does not really fix your problem. All we end up doing is creating a brand new procedure with the same logic as the one before, but Report Caster schedules are still tied to the previous one and so are other internal MRE links.

The only pervasive way to change that would be to hack into the Report Caster repository tables and use SQL to make the updates, then go to the "basedir" folder in the WebFOCUS client, identify your domain, edit the corresponding .htm file and CAREFULLY edit it to change the procedure name .... and I'm afraid that even this may not be sufficient.

Real solution? Ask your developer not to make any spelling errors the first time around (yeah, right!)

1. Create one with the correct name and copy the contents of the original into it.

2. Replace the contents of the original with a -INCLUDE line that points to the corrected version. Document the reason.

3. All future schedules and dashboards should use the new version. When the old version falls out of use you can remove it, but it really doesn't matter if that never happens.

If Report Caster is happy with the underlying misspelling I'd likely just ignore it. The only part of the system that's going to care about the mismatch is the human part, and they see the expanded name. So option two is to just correct the human-readable name and leave the system name incorrect. I'd be surprised if anyone noticed or cared.

J.

What I would do is:

1. Rename the misspelled procedure in the file system.

2. Delete the original file from MRE.

3. Rename the (from 1) to the name you want and import it into MRE.

4. Update the column TASKOBJ in the table BOTTASK in the Report Caster repository.

5. Keep you fingers crossed....

Håkan

Thanks for the help everyone!

I decided to go the route of just creating new files with the correct spelling, and copying the contents into those files.

Our users actually did notice the spelling error, so we had to fix it.

Glad you found a way around it. Would you please edit your original post and prefix the title with either [SOLVED] or [CLOSED] (whichever makes you feel better)?