If you don't know how to write SQL, the best way to learn is to do it with the QBE and then switch to SQL View. Many people object to using QBE because it has limitations they don't like. If you don't know how to write SQL, then don't be proud. Use the QBE. What you'll see is if you have an expression in your select clause that you want to sort on, you can add ascending or descending in the order by clause. When you switch to SQL view, you will see that the QBE copied your expression from the select clause and duplicated it in the Order by clause.
Or, in my case, I work with too many applications to keep hundreds of table names and thousands of column names in current memory so I always use the QBE to at least create my Select query. I am not proud. I am lazy and a lousy typist so for me, QBE eliminates all the early, typos. Then since I only use embedded SQL if it is actually dynamic, I just stick with the querydefs. Taking parameters does not make a query dynamic. What makes a query dynamic is modifying something structural like determining a where clause at run time as you might with a complex search form. Or needing an In() clause to use as criteria or a Top n. If n is variable, the query is dynamic and you need to create it with SQL.