PDF Display in FileproGI

[WILLIAM LUCCA]

So if I had a pdf named "list.pdf" in "C:\Reports" would coding to display it look something like this:
 If:
Then: declare global menucall (8,.0,g)------- - - - - - - - - - - - - - - - -If:Then: menucall=new message ()------- - - - - - - - - - - - - - - - -If:Then: message menucall SEND "(@R,C:\ "{"\Reports\ "{list.pdf,@)"

or do I need to call Adobe Reader with list.pdf as a parameter?

 


    On Monday, November 23, 2015 5:03 PM, Bill Randall <wrandall at fptech.com> wrote:
 

 

On 11/23/2015 4:55 PM, Kenneth Brody via Filepro-list wrote:
> On 11/23/2015 4:21 PM, WILLIAM LUCCA via Filepro-list wrote:
>> I have a client uses Filepro 5.8 for Windows.  Most users have a default
>> printer that uses the fpml type to display reports as PDF's to the screen
>> (destination file PDF:[open]). They have recently installed FileproGI and
>> now when using it, the reports no longer come to the screen as PDF's.  Is
>> there a way to get this functionality in FileproGI?  Does my client need
>> the Developer's tool kit to do this, or is there another way? In either
>> case, what coding needs to be done?
>
> If you are running GI server as a service, then any program it starts is also running as a service.  Windows prevents services from accessing the desktop, unless you select "allow service to interact with desktop" in the service's properties.  (And, even if you do set this, some versions of Windows create a separate desktop on which the service will run, which is not visible to the user unless you do some "magic", which I have forgotten, and other versions will ignore this setting entirely unless you do some other "magic".)
>
> In short, filePro *is* starting the PDF reader, but Windows itself has placed it on a non-existent desktop.
>
> This is the rules of Windows when running services.
>
And, yes, Bill.  The GI Developers Toolkit with Messaging will allow you to send a message to the GI client machine to start the PDF viewer.

Bill



  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20151123/067ca687/attachment.html>