Working fine from command line but not as "subprogram"

[dolphins]

Hi,

I have an AutoIt script that is reading and analysing a text file and then create a PDF of it (with a third party library). This script (.exe / it is compiled) is working fine if I start it in a DOS Box or from the desktop.

If I start this script from inside another AutoIt script (I would call this a "subprogram"), I get other results in my PDF. How is that possible?

Here is the command to start the script from inside the "main" AutoIt script:

ShellExecuteWait($MyBin & "\PDFcreate.exe", "-I -P -AUTO", $PDFPrint & "\", "open", @SW_HIDE)

Is it possible that the calling script can influence the called script?

Regards

Dolphins

[water]

What do you mean by "I get other results"? Do you get an empty PDF, no PDF at all or an unexpected content?

[dolphins]

unexpected content

basically 99% is ok ... but about 1% of the info in the PDF is wrong

Edited November 9, 2011 by dolphins

[water]

You could try to run ShellExecuteWait without the @SW_HIDE flag so you can see if there are any error messages.

[kylomas]

dolphins,

What is the EXACT command from DOS?

I do not see where you are passing a filename to "PDFcreate.exe" in the shellexecute command.

kylomas

[dolphins]

Command line from DOS Box is this:

c:binpdfcreate.exe -I -P -AUTO

So in this command I don't set the working directory. But if I paste this into a desktop link and set the working directory, there is no difference in the result compared to the DOS Box.

The name of the files to read come from a text file (that name is defined in a config file). So I don't need to give the name of the input files in the command line, they come from that text file.

[kylomas]

dolphins,

I see...nice problem. You are going to need to identify some pattern to the difference, or see if there is an error anywhere (as water suggested).

Good Luck and keep us posted!

kylomas

[water]

unexpected content

basically 99% is ok ... but about 1% of the info in the PDF is wrong

Can you post a screenshot of a PDF that is OK versus one in error? Maybe it's an ANSI/ASCII or a code page problem. Edited November 9, 2011 by water

[dolphins]

right now I am trying to get the graphical debugger working on my Win 7 Prof 64-bit ... I get some error from a Ribbon MRU Manager.

I guess I need to get the debugger running to solve this. Thanks for your help in this thread!

[dolphins]

Hi,

I found the reason ... it is not related to AutoIt. It was my mistake.

Thanks for your help and support!