Run Basic is not responding to changes

I was doing a httpget(getaddress$)

I changed the getaddress$ but the program kept getting the older getaddress$

I keep scratching my head why this is happening.

I then put in a for next loop ...

for k=1 to 100
print k
next k

The program would not print the for next action for some reason it kept the old program and did not load the modified program.

I also put in a command

goto[ect]

The program never recognized this statement. There is no [ect] label...

I am still trying to figure this one out.

I don't think the new modify program is getting loaded.

Anybody else having this problem?

I started from scratch with a new page and reloading the program.

I thought that the system would recognize only my new program.

It still retrieved the old gettaddress$... That was weird.

I stored the program in a file and then recaptured it and then loaded to run basic..

Same thing the system would not recognize my code.

The program kept getting the old getaddress$

I haven't seen this happen. Can you post the code which is causing the problem?

getaddress$="getthedatafromthiswebsite"

for k=1 to 100
print k
next k

goto[ect]

dat$=httpget(getaddress$)

print "dat$=";dat$

the for next was never recognized neither was the "goto[ect]"

There was no such label in the program and the system ignored the line of code.

I tried to change it even more and put it in a new start up, same thing happened.

What was going on was a total mystery to me, and where it was getting the code from was
really out of this world.

I opened new start run basic launched in the new browser and the same thing happened again.

For some reason it was not running the code that showed in the program.

Hmmmm! It works for me????

I only made one change by adding a $ after the httpget as: dat$=httpget$(getaddress$)

I get the following error:
Runtime Error in program 'untitled': goto[ect]
Branch label not found: [ect]

thanks for the try and the input.

I can't think of why it happened.

It was really strange that it did not recognize the error.

Weird things happen. I thought it might have been the machine so I tried on the other machine
same thing happened... 2 different systems (windows 7,and XP) and the same thing happened.