WinExec command question
Joe Boyle
atla38 at dsl.pipex.com
Tue Aug 30 06:55:33 CDT 2005
to use the winexec command to view a report disc file created on the server,
you would have to copy it back using a line like that below,
copy "D:\C drive\My Documents\myreport.txt" "\\client_server\My
<file:///\\client_server\My%20Documents\> Documents\"
either as an additional 'run command' in your procedural code or add it to
your .bat/.cmd file; and you would need a lookup file to associate the
logonid with the correct user's server.
The problem is that you still have to click the winexec button in addition
to the 'run report' button.
As for documentation, this feature is available only to apps using PH
servers on Windows/NT; as you will see, there is very little Windows
specific documentation in the help files, it's all Unix or VMS stuff,
presumably because Windows/NT is the latest addition.
If you have access to the knowledge base you must be a supported customer,
so why don't you log a call requesting information on the remote report
viewer ?
Regards, Joe.
_____
From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Syed Shahul Hameed Mustaffa
Sent: 29 August 2005 21:47
To: Joe Boyle; Deskin, Bob
Cc: powerh-l at lists.sowder.com
Subject: Re: WinExec command question
Dear Joe, Bob,
Because so far I couldn't find anything about Quiz Report Viewer, I'm trying
to stream the quiz output to a text file and open the text file via cmdExec
command.
I really don't understand how to find this Report Viewer. I cannot see
anything about Report Viewer neither in Cognos knowebase nor in Axiant Help.
Where can I find some documentation about it?
Regards,
SYED.
On 8/29/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
given that the quiz report viewer knows where to send the output from a quiz
call, (which is executing on the server) presumably it would be possible for
the development chappies in Canada to program the server to send a signal
back to the client to activate the Winexec command.
Regards, Joe.
-----Original Message-----
From: powerh-l-bounces+atla38= dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com ] On Behalf
Of
Deskin, Bob
Sent: 29 August 2005 17:28
To: Joe Boyle; Syed Shahul Hameed Mustaffa; powerh-l at lists.sowder.com
Subject: RE: WinExec command question
I don't believe you can control the client from the server in that way.
Bob
-----Original Message-----
From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
Behalf Of Joe Boyle
Sent: August 29, 2005 12:21 PM
To: Deskin, Bob; 'Syed Shahul Hameed Mustaffa';
powerh-l at lists.sowder.com
Subject: RE: WinExec command question
the problem with that approach is that with thin clients, the run
command executes on the server, whereas the Winexec executes on the
client.
How can you procedurally process a Winexec command to run on the client
?
Regards, Joe.
-----Original Message-----
From: powerh-l-bounces+atla38= <mailto:dsl.pipex.com at lists.sowder.com>
dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On
Behalf Of Deskin, Bob
Sent: 29 August 2005 16:54
To: Syed Shahul Hameed Mustaffa; powerh-l at lists.sowder.com
Cc: Joe Boyle
Subject: RE: WinExec command question
WinExec is an Axiant client operation, typically tied to a button or
menu entry. If you want to run a Windows app or command from a
procedure, use RUN COMMAND.
Bob
-----Original Message-----
From: powerh-l-bounces+bob.deskin= <mailto:cognos.com at lists.sowder.com>
cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
Behalf Of Syed Shahul Hameed Mustaffa
Sent: August 29, 2005 3:15 AM
To: powerh-l at lists.sowder.com
Cc: Joe Boyle
Subject: WinExec command question
Hi Gurus,
Can I call a winexec command from a procedure(UPDATE, POSTUPDATE, etc.)?
Can you plese tell me how I can do that?
Regards,
SYED
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
This message may contain privileged and/or confidential
information. If you have received this e-mail in error or are not the
intended recipient, you may not use, copy, disseminate or distribute it;
do not open any attachments, delete it immediately from your system and
notify the sender promptly by e-mail that you have done so. Thank you.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20050830/5eb3a054/attachment-0001.htm
More information about the powerh-l
mailing list