Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OIA.Xstatus question

Status
Not open for further replies.

keithb03

Programmer
Feb 1, 2005
10
US
While checking this field to see if Xclock is gone, it works great while running on a LAN, however while running the macro through a dialup connection, Xclock still causes problems for us. Any help would be much appreciated. Following is an excerpt of the code where the problem occurs:



set sys = CreateObject("EXTRA.System")
set sess = sys.ActiveSession
set SCR = sess.screen

StartHere:

keyit("<Clear>")
Do While SCR.OIA.Xstatus <> 0
DoEvents
Loop
keyit("IPTT5510<Enter>")
Do While SCR.OIA.Xstatus <> 0
DoEvents
Loop
keyit("<Enter>")
Do While SCR.OIA.Xstatus <> 0
DoEvents
Loop
 
What's a "dial up"?

Just kidding. I've never used it over a slow connection.
Basically the code is moving faster than the connection. You may want to add a "waithostquiet" after the loop to help slow it down a tab.

Alternately, you may want to add another full loop. Seems silly, but I bet you're having a timing problem.

calculus
 
Unfortunately, our on-call staff must use laptops with dialup at night and on weekends. I had the same thought about adding the waithostquiet in addition to the loop. So far, it seems to be doing the trick. Here's how I coded it:

keyit("IITT5510<Enter>")
SCR.WaitHostQuiet(1500)
Do While SCR.OIA.Xstatus <> 0
DoEvents
Loop


Thanks,
Keith
 
I'd probably put it after the loop, but that's just old habit.

calculus
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top