Using PowerTerm Enterprise for DDE Scripting

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jessica - 09 Aug 2007 19:00 GMT

Good afternoon,

I am fairly new to this programming part of Word and MS in general.
I was hoping that someone here would have some PowerTerm scripting
experience, using the DDE commands.

That being said this is what I am trying to do, I am using the host
Meryvon's Host, in PowerTerm Enterprise, to copy and paste three selected
lines via the dde commands custom in the PowerTerm Scripting Langauge that
PowerTerm has built in.
I am unfamaliar with how to do this, so I shall paste the code I am
using.

line1 = [screen 5 11 5 36]
    line2 = [screen 11 26 11 65]
    line3 = [screen 13 26 13 59]
    append line4 $line1 $line2 $line3
    conv = [dde initiate WORD LABELS.DOC]
    dde poke $conv P1 $line4

Does anyone have any idea what I need to put after the P1, or inplace
if it so it will send $line4 to that Word document named Labels.doc?

Thanks,
Jessica

Reply to this Message

Peter Jamieson - 14 Aug 2007 10:07 GMT

See my response to your other question.

FWIW I had a go with the examples in the article I mentioned, and
a. DDEPoke does not appear to work
b. the example using DDEExecute did work, but how exactly you can control
where the text goes is a different matter.

Since it works, you might be able to achieve something along the lines of
e.g.

line1 = [screen 5 11 5 36] {ENTER}
line2 = [screen 11 26 11 65] {ENTER}
line3 = [screen 13 26 13 59] {ENTER}
append line4 $line1 $line2 $line3
conv = [dde initiate WORD LABELS.DOC]
dde poke $conv P1 $line4
dde terminate $conv

Of course I don't know anything about PowerTerm so do not know how to
construct those strings properly.

Peter Jamieson

Peter Jamieson

> Good afternoon,
>
[quoted text clipped - 21 lines]
> Thanks,
> Jessica

Reply to this Message

Jessica - 15 Aug 2007 00:44 GMT

I appreciate the attempt Peter.

I did decide to go with the copy/paste method that is native to windows.

Thanks alot for trying though. Its not a lack of possiblities on Word's
side it is on the PowerTerm Scripting Langauge that is causing the issues.

Reply to this Message