Hello,

We need to use Excel Templates for few of our reports to run some macros on opening a report. This is working absolutely fine when reports are run from WebFocus Dev Studio. But when reports are triggered from ReportCaster, the templates are not picked up. Any help on this is appreciated!

Thank you in advance.

Can you please update your profile signature with your WebFOCUS release and platform?

This will make it easier for us to help you correctly.

The answer could be here:

Excel Template

Thank you Ginny and Francis. I have updated my profile signature.

Francis, I will go through the thread you suggested and hopefully find the solution. Thank you.

Francis,

My template is in a directory under App path but I still have no success when triggering through ReportCaster. Could you please let me know what permissions/privileges I need on ReportCaster for this?

Unfortunately I am not working with a version of WebFOCUS that supports templates so I can't help you. Hopefully someone else will.

YOUR version did not appear on your post. Unfortunately, like Francis I can not test this for you, but my experience with templates in 7.1.3 was that they would not work with report caster. The final step in creating a template had to be ON TABLE PCHOLD. This may have changed in newer versions.

I read the doc for 762 and it does support templates for Report Caster. But I don't know if it only works on Windows implementations (which I don't have) nor do I know enough about Excel to do a template.

Helme, you have to update your signature in your profile in order for the release stuff to show.

I have a mass of jobs that run via report caster creating Excel Templates, you just have to understand that you will not be able cast the resultant Excel workbook, but you could cast an email with a hyperlink to the file providing that it is accessible by the recipient.

Basically you just perform FILEDEFs for the interim template hold files and FILEDEF the final one to a physical location accessible by the Reporting server.

FILEDEF Templat1 DISK R1234EX1.mht
FILEDEF Templat2 DISK R1234EX2.mht
FILEDEF Templat3 DISK R1234EX3.mht
FILEDEF Templat4 DISK R1234EX4.mht
FILEDEF Templat5 DISK R1234EX5.mht
FILEDEF FnlOutpt DISK "[drive]:/folder/subfolder/filename.xls"

T

Thanks for all your posts.

Pat, I am using version 714, do you think templates will not work with this version too? According to Ginny 762 supports templates, does that mean earlier versions do not support templates?

G

G,

Look at the list of supported output types when you are creating a task. That will tell you whether it is supported or not. Also the Report Caster manuals have lots of information in them.

If that doesn't help, you'll have to open a case.

Thanks Ginny. I will check it.

Templates work fine with 7.1.3. in general. You will probably have to use Tony A's solution to create that output with Report Caster.

Thinking outside the box, and without the benefit of having "ON TABLE [PC]HOLD AS .... FORMAT EXLTEMPLATE" to give you an .mht web archive file, how about creating your BYTOC Excel output to disk and then running a VBScript to add the VBA code modules into the resultant file? In fact you could use VBScript to completely process the output file exactly as you require without having to resort to using VBA internal code and the syntax within VBA and VBScript is very similar.

One thing that I would urge you to do if you were going to use this approach, is to actually save (via VBScript) the ultimate file in "proper" Excel format as this could result in a massive space saving. The ones that I create average around 60% space saving.

It could work.

T

Helpme,

Templates work with 7.0 and higher, my experience with them was at another company where the highest version we had while I was there was 7.1.3. The problem with using templates with Report Caster is that your final hold has to be ON TABLE PCHOLD. Since you are having to hold them to a "PC" there is nothing to cast.

Tony's suggestion of casting an email with a hyperlink is absolutely brilliant, but I think it will only work if you are running on a windows server.

Thank you all for your posts.

But how can we add a VBAScript to resultant files? Should we do manually?

Sorry, didn't I mention that? Oh wait a minute, yes I did

quote:

and then running a VBScript to add the VBA code modules into the resultant file

T