Search results for query: *

I have the "waitlist" section of code in an include file because I use the same code in multiple scripts. So, my include file looks like this: ;--------------------------------------------------------------------- ; Procs.inc (procedures "include" file) ; This include file contains...

Well, I said I'd report back. I modified WaitList to allow up to 5 strings to wait for. It works as it's designed... that is, it looks for one of the strings sent in to the function, if it doesn't find one, it times out and the response is sent back to the script. Thanks again.

I tried using WaitList, but for some reason, that didn't work either. I modified it to have up to 6 strings and WaitList came back with value 0 (none). I'll try again, just for S & G and I'll report back... but I don't believe it's going to make a difference.

See my previous post here. I thought I'd figured out the problem. And the script's been working fine. But, I added more lines to be watched for and it didn't work as I expected it to. I'm connecting to Medicare's claims site. In my script, I wait for the logon prompt, then send a user-ID...

Hmm... while adding my code I *DID* spot something that makes me go like this... From my PasteBin post, line 352 has a waitfor cmd. Then, if they only upload files (iRecvFiles is 0), the script hits another waitfor prompt at line 390. If you have a waitfor followed by the exact same...

The code doesn't appear to be skipping around at all. The transfer "above" the section in question goes just fine. I saw that was your preferred way, from your code samples. I forget why I wasn't using that... seems I had seen something somewhere that said $XFERSTATUS wasn't being updated...

I'll do even better. The entire script can be found at PasteBin. The line in question is highlighted in yellow.

Okay, I've got a screen capture of the last portion of the monitor window. You'll see that at the end of the script, I actually do send the logoff command. That's because I've had to remove the "FOREVER" timeout value from my script. It simply waits then sends the text to the screen. This...

Well, I was able to monitor the information going out and coming in. Nothing unusual, no odd hex values, simply the text followed by a carriage return and line feed. Same thing as what I saw in the capture file. Any other ideas?

Yep, that's what I was looking for. Thank you!

Also, FINDSTR works quite well. If you want to find any line that has "PICKME!", you'd key findstr "PICKME!" infile.txt > outfile.txt To ignore upper/lowercase comparisons, use the "/i" flag: findstr /i "pickme!" infile.txt > outfile.txt Typing findstr /? will give you more info.

Several users have complained about the way the files are listed in the DirListBox - that is, they can't see anything other than the file name. Is there a way to display files with their dates, type, etc? I'd prefer to use the Windows OpenFile dialog, but have no clue how I'd do that. Anyone...

** Moved this request to a new thread **

My script is failing at the "waitfor" command, not recognizing the trigger text when it's displayed on the screen. I've created capture files and recorded scripts to make sure I look for the correct text coming across the screen, and the capture file and script both show the same data that I've...

Okay, follow up question. Several users have complained about the way the files are listed in the DirListBox - that is, they can't see anything other than the file name. Is there a way to display files with their dates, type, etc? I'd prefer to use the Windows OpenFile dialog, but have no...

That's probably it. I haven't had a chance to get back on the client's machine to verify but I'm satisfied with this answer - thanks!

I have this script at several different customers and have never run into this problem until today. And boy, is it frustrating! I'm displaying a directory listing to allow the selection of multiple files to be uploaded. I have a filespec string of "md*.*" to restrict the display. The problem...