My mistake. Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Que, Jason Sent: Wednesday, August 20, 2003 2:06 PM To: '[EMAIL PROTECTED]' Subject: RE: [Talk] PauseLoop issue I would use condition like: If Row = 10 And Col >= 55 And Col <= 60 Then Enter 'Discharge Time Jason Que Information Services Saint Louis University Hospital (314) 256-3528 > -----Original Message----- > From: Rich McNeil [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, August 20, 2003 12:47 PM > To: [EMAIL PROTECTED] > Subject: RE: [Talk] PauseLoop issue > > Lew, > > There's an issue here of pausing for titles in a loop. In the command: > > PauseLoop "Discharge [EMAIL PROTECTED],37", "~" > > "Discharge Time" is always at row 10 column 37 while you're on this screen > so it's not a valid indication that your application has this as a prompt. > A better condition would be: > > If Row = 10 and (Col >= 55 Or Col <= 60) Then Enter 'Discharge > Time > > This handles the double column issue and the possibility that the cursor > might be anywhere in the field. (The Loop command should also have a Row > and Col condition.) A problem with this is that is does have the "the > second time false" feature of the At/PauseLoop command so that if the > application were slow, it could press multiple Enters. I'd use a Stable 1 > to limit this effect. You should only need a single Stable at the end of > your loop. > > There's also an issue with using prompts from the first column (e.g., > Admit Date) since they also are satisfied when the cursor is in the second > column. The If Row... format will also work for these conditions. > > Finally, I noticed that you've ordered the conditions in your loop in the > reverse order that they appear. This is an excellent idea because it > ensures that the Stable command will always be executed after any > condition is satisfied. > > > > Rich McNeil > Boston Software Systems > 866 653 5105 > www.bostonworkstation.com <http://www.bostonworkstation.com> > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 20, 2003 12:28 PM > To: BostonWorkStation Talk > Subject: [Talk] PauseLoop issue > > Well, I call it the pauseloop issue, but I am not sure. > See the attached doc. > > My issue is that I have a two column screen, and I have had various issues > while trying to run this. > > The original issue was that I couldn't get the cursor to stop on Discharge > Disp. I figured that out. It was because strings in the second column were > being statisfied by strings in the first column (I would want to PauseLoop > on Discharge Date, but in my Do Loop Admit Date was also being satisfied, > so an enter would be keyed, and I would end up 2 or 3 fields beyond > Discharge Disp). > > I have ended up trying to be specific about Discharge Date, by adding > cursor positions, but that is not working right now. > > Any suggestions? > > TKs > > Lew Hundley > Information Specialist - Programmer > Silverton Hospital > Silverton Oregon > 503.873.1657 > [EMAIL PROTECTED] > > >
