[encom]

>w3schools PHP tutorial

I think a better approach is to think of a (very basic) project you want to create, and then claw and bite your way through it, until you have something that works. Then think of a way to enhance it, and go though the process again. Slogging through a tutorial is boring, and you have nothing to show for it when you're done.

PS: Don't listen to sneaky JavaScript evangelists. Wicked! Tricksy! False!

[meowster]

Lol, I appreciate everyone's advice, and I'll have to do research on it all to see what will work best for me.

I'm just reminded of Derek Siver's experience where he started CD Baby with PHP, and then tried rewriting it in order to use something other than PHP just because, but ended up sticking with PHP. Though he is a musician and not a professional programmer. However I'm not a professional programmer either, and I don't really want to become a sys admin to maintain the servers etc.

[HoppyHaus]

Agreed, that's how I learned. Also run it by someone that knows PHP so they can yell at you. I've used prepared statements ever since then