Basic autoit script for Crystal Reports v10

[geminatores]

Hi to all. I'm totaly green and strugling to get my exe script working on CR v10 and Windows 7 all was working fine on XP machine and CR v8.5. Here is the script:

Dim $sReportName 
Dim $objCRApp 
Dim $objCRReport 
Dim $CrystalExportOptions 
Dim $ExportFileName 
Dim $ExportType 
$sReportName = "C:\QS\report.rpt" 
$objCRApp = ObjCreate("CrystalRuntime.Application.10") 
$objCRReport = $objCRApp.OpenReport($sReportName) 
$CrystalExportOptions = $objCRReport.ExportOptions 
$ExportFileName = "C:\report.xls" 
$ExportType = 29 
$CrystalExportOptions.DiskFileName = $ExportFileName 
$CrystalExportOptions.FormatType = $ExportType 
$CrystalExportOptions.DestinationType = 1 
$objCRReport.Export ( False ) 
Sleep(500) 
WinWaitClose("Export", "", 60) 
GUIDelete()

 

I receive error: Line 16 The requested action with this object has failed. Any ideas how to fix it?

Edited July 5, 2016 by JLogan3o13

[Jos]

You probably want to start with adding a COMErrorHandler to the script and display the error details for the COM object. (Search for COM Error Handling in the helpfile for an example)

Jos

[mLipok]

Welcome to the forum.
First please read this:  * How to post code on the forum *

And do not use Dim to declare variables.
You should use Global / Local instead Dim.

You also should use COM ERROR Handler , I mean you should read about

ObjEvent()

 

mLipok

 

[geminatores]

Yes sorry about that code paste. So if my script is worthless could you paste me correct basic script for export XLS and PDF from Crystal Reports? I'm no coder/programmer for sure so I will not be able to add COM ERROR Handler to the script

[mLipok]

1 minute ago, geminatores said:

Yes sorry about that code paste.

Could you plesae edit your first post ?

1 minute ago, geminatores said:

So if my script is worthless could you paste me correct basic script for export XLS and PDF from Crystal Reports? I'm no coder/programmer for sure so I will not be able to add COM ERROR Handler to the script

We are teaching how to catch fish, but you must make step by step progress.

Moreover, I doubt that anyone here on the forum, using this particular solution in conjunction with AutoIt - of course this is possible.

So you have to be our eyes and hands, we will be your head/mind.
Think of it as an exercise - you have to get involved

 

[Jos]

7 minutes ago, geminatores said:

I'm no coder/programmer for sure so I will not be able to add COM ERROR Handler to the script

Doubt you even opened the helpfile, like I suggested! 

Jos

[mLipok]

@Jos this is even easier than opening HelpFile ...

@geminatores as I suggested before:

23 minutes ago, mLipok said:

You also should use COM ERROR Handler , I mean you should read about

ObjEvent()

 

Just click the above mentioned function name.

 

[Jos]

Not starting a discussion on this but: hitting  F1 and typing the search word I gave and then reading the page on COM can't be too difficult to preform or else one should seriously reconsider coding all together. In other words: It doesn't hurt to put in some effort.

Jos

Edited July 8, 2016 by Jos

[geminatores]

Thank you for editing my post I could't find edit button (is it available for noobies?). Of course the first thing I did was to read about com error handler and checked your link about ObjEvent. And I dont understand anything from that, where or what to put in my script to get it work. My highest achievement in autoit was to get above script working on XP and CR 8.5. So please have a little understanding for my autoit knowledge.

[mLipok]

add this function to your script:
 

User's COM error function. Will be called if COM error occurs
Func _ErrFunc($oError)
    ; Do anything here.
    ConsoleWrite(@ScriptName & " (" & $oError.scriptline & ") : ==> COM Error intercepted !" & @CRLF & _
            @TAB & "err.number is: " & @TAB & @TAB & "0x" & Hex($oError.number) & @CRLF & _
            @TAB & "err.windescription:" & @TAB & $oError.windescription & @CRLF & _
            @TAB & "err.description is: " & @TAB & $oError.description & @CRLF & _
            @TAB & "err.source is: " & @TAB & @TAB & $oError.source & @CRLF & _
            @TAB & "err.helpfile is: " & @TAB & $oError.helpfile & @CRLF & _
            @TAB & "err.helpcontext is: " & @TAB & $oError.helpcontext & @CRLF & _
            @TAB & "err.lastdllerror is: " & @TAB & $oError.lastdllerror & @CRLF & _
            @TAB & "err.scriptline is: " & @TAB & $oError.scriptline & @CRLF & _
            @TAB & "err.retcode is: " & @TAB & "0x" & Hex($oError.retcode) & @CRLF & @CRLF)
EndFunc   ;==>_ErrFunc

and use this line:

Global $oErrorHandler = ObjEvent("AutoIt.Error", "_ErrFunc")

for example at beginning of your script, to initailize COM ERROR Handler.

 

btw.
I have few question:

What is your native language ?
If my explanation helped, I want to know: What was not clear in the documentation ?

mLipok

 

[geminatores]

Thank you for the answer. I'll check it afternoon. My native language is Polish, sorry for poor English but I don't have many opportunities to use it  In the ObjEvent documentation I didn't have any idea where to paste com error function. It should be like: copy this function into your script at the beggining and voilà it works. Now all is clear for me

[mLipok]

Thanks for your answer.

[geminatores]

Well I've added COM ERROR Handler function and nothing changed, still the same error.

[Jos]

No, it should at least tell you more. so what is it telling you? If nothing than please show the code.

Jos