Using the wizard the tags come out as follows: A 0 first here A 1 second here A 2 third here A 3 4th here. When I placed the 0 thru 3 in the tagvalue it failed click any of them. ### Click the second here ### Let>FrameName={""} Let>FormName={""} Let>TagValue={"1"} LibFunc>hIE,ClickTag,r,%IE[0]%,str:...

Boy your html stripper is working great, nothing gets by. I will try to send the file without the code to make it look like html. tom1.htm here tom2.htm here tom3.htm here tom4.htm here Just picture the above files as placed in the html format so that when you click each here it would go to each spe...

Thanks Marcus, but I must be slow, I still can't get it to work. The test.htm file looks like below... ? represents the FrameName={""} Let>FormName={""} Let>TagValue={"?"} LibFunc>hIE,ClickTag,r,%IE[0]%,str:FrameName,str:FormName,A,TEXT,str:TagValue ### Click on the second here link ### Let>FrameNam...

Using the Recorder, how do I change the script to make it select the second "here" on the page. Click here Click here The code below was done using the Wizard but the little bugger only selects the first here and none of the others. I think it is something to do with the index = 0 or index = 1 for s...

I monitored all that during the debug. I used MessageModal>%FieldName% %FieldValue% thruout the script and it always had the correct data including the use_name and the correct user name. Even along the border, the monitor showed that FieldName was being set to "user_name" and FieldValue was being s...

Ok thanks for the help anyway, I guess I have a strange computer. Last year I was running XP and the httprequest command caused a lock up if you called it more than once and we never could figure that one out either, and no-one else could dupe it. Ichanged to XP Pro and that problem went away. Guess...

It works wonderful for me also on win98 and all the computers I don't need it to run on. My computer is running XP PRO and I think it is the reason it won't work. Has there been a lot of XP Pro testing also? Even on Win98, I needed to use the {"user_name"} but you are right it works fine. Just not o...

However the below works fine, if I change it in the source also and as we know that won't be possible normally. I changed it in the test source fine.

*************************
Let>FieldName=user_name_1
*************************

Quote from above:
***********************************************
I tried this but no work: Let>FieldName={"user_name"}
***********************************************

OOPS! You may have mis-understood the problem. The problem is not with FieldValue=tommytango, the acutal problem is with the FieldName=user_name. I tried this but no work: Let>FieldName={"user_name"} You gave me a fix for FieldValue vice FieldName. Let>FieldValue={"user_name"} ### Enter user name ##...

You are soooooo.... good! Thanks for not saying why don't you just use a different variable. Of course I can't do that as I am scripting someone else's program. They probably would not take kindly to me telling them to change their program so I can script it better. Especially when they don't want m...

Degolg, They have a lot of absolutely great batch scripts for photoshop within the photoshop environment. Not to say mjt macro won't work great also, but I have used the batch processing there and they drill down just like you wouldn't believe. Its almost like the mjt recorder that works so well her...

Ian What a great tip! Use /c to get file name only. I been doing dos for 20 years and never came across that. I have used the dir > temp.txt for years to get a directory into a file and then had to write the prorgam to get rid of all the other un-necessary directory junk. Thanks again. I wil be usin...

I'm back. I apologize if this shows up someplace else, it disappeared so I sent it again. If duped somewhere, pls delete and accept my apology. I just seem to get out of one mess into another, the recorder was doing fine till I got to this problem. I know it is not a fault of the recorder, but a fau...

Tom Chambers said: Thank you! Thank you! Thank you! That worked fantastic. (referring to the macro fix above). I was having the same problem as you, it would not work on a subroutine so I am glad you switched to a function. I would have never thought of that. Thanks again for the immediate response....