Since you sound super-frustrated right now, I would suggest you do something easier, maybe a breakout kind of game. You could do it in 2D and it would give you a sense of accomplishment to finish it.
I would suggest drawing all of the sprite images with MS paint (or whatever paint program you use) onto one bitmap, noting what the coordinates are for the different sprite images. I would suggest you put them at similar intervals on the bitmap so you can easily grab the images.
You program the ball movement and get it working so that it stays in bounds. Once you have this, you put in the player's paddle and give the user control over it, again checking to make sure it does not go off screen. Have the ball react to the paddle and bounce accordingly.
As far as the 'bricks' go, I would set up an array to show which images are where and their status. I actually prefer to use my arrays for collision checking with 2D games instead of the built-in collision commands.
You check for collision between the ball and the bricks. When a brick is destroyed, you add to the player's score (which should be displayed onscreen somewhere). When all of the bricks are destroyed from that level, you go on to the next. You decide what is in each level, what type of bricks you will use, how many balls a player can have at one time, etc., etc.
Later on, you could decide to animate the ball and have it appear to be rotating the direction you are moving, you could have bricks give powerups where once they are hit, the powerup falls down to the player, you can expand and contract the player's paddle. . . the list goes on and on.
It's really great fun once you get the hang of it, but there is a bit of a learning curve at first. Hang in there, it will be worth it if you do.
LB
