I'm not suggesting that you "abandon ship" and just not continue coding, but ... you aren't really approaching it very well and could use spending some time thinking about the project before you start tapping on the keyboard.
That code doesn't compile: that's one problem - and a relatively simple one under normal circumstances. But you haven't tried to work in "small chunks" so you have built a lot of code based on code that doesn't compile, so you have no idea if it will even work when it does!
And frankly, that code doesn't show much evidence of planning which means you end up with rather a mess to try and get working.
So I'm going to recommend two of my articles for you to read, and hopefully get a better starting point to work from:
How to Write Code to Solve a Problem, A Beginner's Guide[
^]
How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[
^]
Read them, and then start from scratch: design, code a small bit, get it to compile, run it, test it, fix it, test it again. When it works properly move on to add another chunk. It may seem like a slower way to do it, but it saves huge amounts of time in the long run.
So don't give up - just try to work smarter, not harder! You'll get there.