I discovered this difference between QB and QB64... [My mistake. No Difference.]

[Cobalt]

I'm with Fellippe, the example you stated to error out seems to work fine with no errors in QB45.

[bplus]

Maybe Pete's Peeked and Poked one too many times?

[Cobalt]

Maybe Pete's Peeked and Poked one too many times?

you mean "and been Poked" Darn aliens!

did QB45 come with California's "Prop 65" warning? Maybe he can sue!(cause everything in Cali' causes cancer, even the air)

[MWheatley]

Runs here, too, in QB45 and PDS 7.1, although I haven't tried in QBasic, as that's not presently installed on this machine.

Malcolm

[Pete]

@FellippeHeitor  Well I got back, read the posts, and dug up the old Win 7. I didn't save the code from before, so I typed it back in QuickBasic, and ran it in DOSBox. So this time, the program with DIM ran to completion. So whatever happened before to make it  throw a subscript out of range error did not happen this time, and as we all know with computers, that means whatever I did last time was not the same. So my apologies. I don't know if this was some senior moment or eyesight situation, because my DOSBox renders a very small IDE. Now I wished I saved the damn snippet, so I could see what happened. My best guess is I may have typed a different variable like a1$(11) instead of a$(11). Anyway, a "blonder" moment indeed.

Conclusion. QB and QB64 act exactly the same way in the situations described.

Pete   

[FellippeHeitor]

Glad it's cleared now. Thanks for confirming.

[Cobalt]

No excuse!

You are here by sentenced to....

20 years hard coding!

“Start codein’ ya doggone long eared galoot”

[Pete]

You mean like this?

Code: QB64: [Select]

1. DO
2. PRINT "Eat me, varmint!"
3. LOOP UNTIL HellFreezesOver

Look on the bright side, at least you got me to try CamelCase.

Pete