>>>>yes, it should be do pdfoutput with myReport.frx
>>>>If i run this command in "Command Window" , It works great
>>>>However, When I place into the "Print button" . it can't run
>>>
>>>Did you note what I wrote about avoiding absolute paths?
>>
>>Tore,
>>
>>I think the author of Frx2Any advocated otherwise, though I'm also not familiar with the product.
>
>Regardless of the component requiring the filename, the absolute path should never be hardcoded in the app. Of course, most of the external components require one, which is the reason why we need to use fullpath() so often.
>
>My rule of thumb is that my app should be able to be installed anywhere, be able to find its files from their relative paths, and all external components (be it automation, or one of ProfileString API functions or whatever) should be supplied with full paths to any filename they require. Which is actually not hard to do at all with all the file/path functions we have.
>
>So: hardcoded paths no, relative paths inside the app yes, absolute paths derived from them yes.

Agree. Basically, we should always use relative paths and pass fullpath("Myfile.frx") to the external application or component.