Try this Syntax: VARIABLE_%COUNTER% I use this w/o the {} to import my variables. MS has done everything I can imagine so far. You may want to read the variable into another variable first. If you decide to send multiple items from your array to the subroutine I would try something like this: Let>Ad...

Const ForReading = 1, ForWriting = 2, ForAppending = 8 Dim fso Set fso = CreateObject("Scripting.FileSystemObject") MySubje() Private Sub MySubje() On Error Resume Next Dim strFileName ' Full path and name of file. strFileName = "k:\test.txt" Set fLog = fso.OpenTextFile(strFileName, ForAppending, Tr...

I'd like to kick off a rename of a file as soon as it is written, but I am not sure how to tell when the program has released the lock.

Thanks!

I'm not sure if your looking for something different, but I just open up the properties, and type in the version number on the summary tab. Revision number is under advanced on the summary tab. Alternatively if no one really changes anything on the file you can just use the modified time/date stamp ...

I'm not sure if this is helpful, but I don't think version 11 was designed for windows 7. I think you have to go to Version 12 to use with windows 7.

-John

Thanks for the additional link, this confirms what I had assumed.

Scripting only supports the on error resume next syntax.

I was hoping for an on error goto errorhandling or something like that.

I've been trying to goto a specific sub when an error is detected, but everything other then on error resume next seems to cause a compile error, any idea why?

-John

Yes Refocus windows is on.

Hey that's a great idea thanks for that idea,

I don't know why a screen capture never occured to me.

I'll use that for trapping failures go forward

Thanks

-John

Hey I just wanted to say I love this tool. It can do literally anything with a little creativity. However, I do have one frustration. So many of my macros are image based that I am really struggling to use the debugger. Each time it goes to the next line it pops MS to the front and kills my script. ...

I've found that if you just display the mail item instead of attempt to send it you can get around that nasty error message. I then just follow it up with a Press CTRL press Enter Release CTRL and it goes out w/o any problems :) Extremely reliable and fast. I've found that by altering the VB code th...

Your correct, the only time the active window is collected is when it fails. It is extremely difficult to log onto this specific application, as a result, as part of my efforts to finally get to a point where I can have a reliable login I've been collecting the active window to help me troubleshoot ...

Hi,

How will it know when to stop?

Thanks for taking a look. I've moved onto another way of handling it, but still don't understand why the code didn't work.... Here is the raw code: This script is to log onto our accounting software which they say can't be done by macro software. (I have figured out how to do this reliably with anot...

This was in the log file of a script I have running. I have no idea why it failed, and I'm sure there was no window open that was only $. Any idea why it would have failed? Where that $ is comming from? -WJF IfWindowOpen>Select Company 3/21/2010 21:30:25:907 - END: else 3/21/2010 21:30:25:907 - STAR...