One thing I usually do is break it down step by step.
Firstly get your hardcoded SQL working:
"SELECT * FROM Table WHERE Field = 'Item'"

Then start splitting it out
"SELECT * FROM Table WHERE Field = '" & "Item" & "'"
Run that and confirm it still works.

Then you can swap it for a Param
"SELECT * FROM Table WHERE Field = '" & FIELD & "'"

I've used single quotes for ease but ref Double Double Quotes for further help.

Thank you Alex.

The use of single quotes helps immensely with being able to follow along.
I'm starting to understand the theory, now i just need to practice.

In my recent project i have been doing more manual SQL writing instead of using the query designer.
It's really good fun learning something new.

It's a skill worth practicing, and as with anything the more you do the better you'll get. It'll soon become second nature and it'll likely be faster than using the drag and drop version.
Plus if you ever move to MS SQL Server you'll thank yourself.

You're doing exactly what you should be doing: getting the basic theory down, then practicing it in real situations.

Alex is right that breaking the SQL string into pieces is one of the best ways to troubleshoot it. I like using a visible mySQL text box while building searches for that same reason. If you can see the final SQL statement that Access is receiving, it is much easier to spot a missing quote, space, wildcard, or AND condition.

And yes, writing SQL manually is good fun once it starts clicking. The Query Designer is great for getting started and for quick ad hoc queries, but knowing SQL gives you much more control.