Search results for query: *

It turns out that after a week on this, cognos acknowledged that there is an issue with Impromptu 7.1.339 and Windows Server 2003. They had me upgrade to 7.1.814 and the ExportExcel Method now works.

My first question was kind of tongue and cheek. My sarcasm didn't quite come across in my post. :) I think for now I'm going with the clipboard solution. It was pretty easy to clear out the clipboard and it will basically cause the least amount of impact to the users. I'll save off all the...

Are you sure the path that you were trying to export the excel file to exists? At least that is what Cognos came up with after looking at this for 3 days. Sheesh. I'm glad the money we pay for support is well spent. We are currently using ExportExcelWithFormat as a workaround for now, but...

That macro works. The two boxes are running the same version of Office and Both are running Excel 2002 (though the old box has SP3 versus SP1 for the new box). They are both running Impromptu 7.1.339.0. They are on different operating systems with the old being on XP and the new being on 2003...

The line that errors is: imprep.ExportExcel ExcelReport I also tried your code and still get the R438 error.

I'm stumped too. The other thing I noticed in testing this is that it actually does do the export to excel and the file is in the directory where I would expect it to be. The problem is that there is still the error in the code and it still locks up the macro when compiled. I read a post...

Yes. That was my first swing at this. I installed Excel on the new server, as well as access, word and the rest of the office suite.

Hello. We are currently migrating our cognos impromptu reports to a new server. We have a bunch of macros that run the reports and export them to Excel. However when installing cognos on the new server, the ExportExcel method no longer works in the macros. I've heard that this has been...

I think that is what I'm running into. I added the error trap logic to my macro and ran the macro. The report still hung up when it encountered an error.

We currently run all our reports from macro files that are executed from windows scheduler. A problem we sometimes run into is that a report will run and encounter an error (possibly that the database is not available). What this does is hang the impromptu session until the message is...

Actually I've been toying around with some things and we kind of got it to work. We find the same issue as you, however, in that it leaves an impromptu session open. It also matters which of our report batches try to set up impromptu as multi session. We're going to keep digging at it.

Hi all. We are currently running our impromptu reports from mcx macro files. These are then batched up in DOS .bat files. The problem we are running into is if two of these batch files are open at the same time, ie one starts before the other is finished, the second does not open up its own...