If your only concern is remembering the syntax when coding, then I'd say to you that when you are on the job you can use reference books or do a web search to find the syntax information.
However, I think I read one of your responses to responses that you feel you have problems "getting started" with a program but once you get started you like it. You might want to clarify that somewhat. What kinds of problems do you have? Do you mean getting started with a language? Or do you mean understanding the issue your code needs to solve? Each of these are different issues and would need to be treated differently.
If the problem is that you have problems getting started with a language, then you might just need to relax a bit and give yourself the time and space to learn it naturally. Alternatively, perhaps you aren't truly motivated by this because you are trying to create a "hello world" application which you know is virtually useless. In this second case, try writing something that you think might prove to be a useful tool for you in the future.
If you feel that you have a hard time understanding the requirements you program has to meet, that may be a bit tougher. In this case you might need to focus on softer skills like communications. I've seen plenty of times where a programmer and a business person need a translator (and, yes, both were ostensibly speaking English at the time!).
Perhaps you mean that you understand the requirements, but you find yourself wondering where to start coding. If this is the case, I found that I had (and on rare occasions still do have) this issue. If you have talent as a programmer then as you gain experience you will learn a "programming style" that will guide you on where to start.
Again, I don't know what you mean by "problems", nor do I know what you mean by "getting started". If you clarify these, you might get some better feedback.
If you are still unsure about this, then maybe look for an internship position or part-time job that involves programming. This will help you figure out whether you like it or not. You could also look for similar positions in other technology fields to help you find which one you like most. Be aware, however, that a decent job at one company could be horrible at a different one (and vice-versa).
I will also echo the sentiments of at least one other person. If you don't love the technology, you might want to consider something else. That's why I suggested the internship/part-time position. This will get you a feel for it in a "real" situation.
At a minimum, this "trial" position might get you close to some preople so you can ask them what their job entails, whether they recommend it, etc. Don't be afraid to ask them -- people often love to talk about themselves. If they realize you're a student, it'll probably spark some nostalgiac feelings of when they were in school and searching for their future profession.
That brings to mind another avenue to pursue. See if you can find any programming groups in your area and see if you can come to their meetings. This again gives you direct access to people who are in-the-know and may help you.
As for fields in technology not directly related to programming that may be good for you, that's tough to say without really knowing your personality.
If you are an extrovert, then you might be suited for a help-desk or similar position (but be warned -- if you are an introvert, such a position will seem like a living hell).
You might consider network administration. These people rarely program (except for the occasional login script). Most often they become the people who set up hardware, load the OS and install new software on the machines when it needs done.
Database Administration is another role I've worked in. Depending on your database vendor and your final job, this might require a LOT of "coding" or very little. Either way, some essential tasks will require knowledge of SQL and/or DDL (Data Definition Language).
You might also consider computer-related security degrees. Or even something to get you into an auditor role.
Some other (somewhat indirect) positions you might consider include the following:
* Technology trainer
* Auditor
* Data Communications Specialist
* Graphic Artist (specializing in web graphics)
* Technical Writer (if you have good writing skills; otherwise nix this).
As you can see, there are plenty of alternatives. In fact, a lot of jobs that people normally consider "non-technical" can be done with some kind of technology focus. In the event that you find technology "interesting" but don't want to live and breathe it, pursue one of these other jobs as a career (but with a technology focus, perhaps).
